filesystem-mcp-guardrails skillA
filesystem-mcp-guardrails is agent-read markdown (skill) from yeaight7/agent-powerups: Use when designing or reviewing filesystem MCP access, path boundaries, allowed roots, method allowlists, and safe local file operations..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Filesystem MCP Guardrails ## When to use Use when configuring, reviewing, or debugging a local filesystem MCP server — particularly when deciding which paths to expose, which methods to allow, and how to enforce workspace boundaries. ## Safety Model The core constraint is **strict path bounding**: the MCP server must only operate within explicitly declared workspace roots. No exceptions. | Principle | Rule | |---|---| | Scope | Bind to the project workspace directory only — never `/`, `~`, or OS dirs | | Access | Start read-only; add write methods only when the use case requires them | | Methods | Use an allowlist — block delete/move/rename by default | | Secrets | Never expose `.env`, credential files, SSH keys, or token stores | | Approval | Always require user approval before starting a new MCP server process | ## Configuration Checklist Before starting a filesystem MCP server: - [ ] Allowed roots list is explicit and scoped to the project directory. - [ ] No root is set to `/`, `~`, or any system-level path. - [ ] Method allowlist is defined (e.g., `read_file`, `list_directory`, `search_files`). …
Read the whole file at its exact version.
How to install
mdr add yeaight7/agent-powerups/filesystem-mcp-guardrails@git:20260515.a1b057cmdr add yeaight7/agent-powerups/filesystem-mcp-guardrails@sha256:b8e0e92693490173Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_a6yh4owziuhahzfm)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260515.a1b057c latest | 2026-05-15 | a1b057c | 3,288 B | A | view · diff |
| git:20260505.3616562 | 2026-05-05 | 3616562 | 1,660 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3288 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
yeaight7/agent-powerups · 6 stars · license Apache-2.0 · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_a6yh4owziuhahzfm GET https://markdownregistry.com/api/v1/resolve?ref=yeaight7/agent-powerups/filesystem-mcp-guardrails GET https://markdownregistry.com/api/v1/blob/b8e0e92693490173a73b9a9f16c6d1630a3c84d9ad84c15f2cfb12ff869da948
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from yeaight7/agent-powerups
Every file in yeaight7/agent-powerups