Skill

filesystem-mcp-guardrails

Use when designing or reviewing filesystem MCP access, path boundaries, allowed roots, method allowlists, and safe local file operations.

npx claudepluginhub yeaight7/agent-powerups --plugin tool-integrations

Popularity

Parent stars

Parent forks

Shared by

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/tool-integrations:filesystem-mcp-guardrails

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

This is a conceptual document for a Filesystem MCP server configuration. It is NOT a runnable configuration file. The earlier research used a Go-based filesystem MCP shape; this skill keeps only the safety model.

Supporting Files

references/path-boundary-checklist.md

SKILL.md

34 lines · ~415 tokens

Similar Skills

algorithmic-art

147.3k

Creates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.

3 files

document-skills

Stats

LanguageTypeScript

Parent stars5

Parent forks1

MaintenanceExcellent

Last CommitMay 6, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

Filesystem MCP Guardrails

Status

Intent

When packaged as a true Agent Powerup, this will provide guidance on configuring and safely running local filesystem MCP servers.

When to use

Use when the agent needs structured, protocol-driven access to the local filesystem beyond its native capabilities, or when integrating external tools that require filesystem access via MCP.

Safety Constraints

MCP servers providing filesystem access MUST be strictly bounded to the intended project directory.

Avoid configuring MCP servers with root or wide-ranging access.

Always require user approval before starting a new MCP server.

Prefer read-only operations until write need is explicit.

Keep allowlists for roots and methods; avoid broad recursive delete/move surfaces.

Log configured roots without exposing sensitive path contents.

Required Shipping Work

Before this becomes a shipped MCP config:

Define target-specific config files for Codex, Claude Code, and generic MCP clients.

Add apx mcp check metadata and dry-run install behavior.

Validate path boundary behavior on Windows and POSIX.

Add tests for refusal of out-of-root paths and dangerous methods.

References

references/path-boundary-checklist.md