12 tools. 5 can modify or destroy data without limits.
5 write tools that can modify data. Rate limits recommended.
Last updated:
Write operations (fs_copy_directory, fs_create_symlink) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Execute tools (fs_batch_operations, fs_build_index, fs_stop_watch) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
Intercept sits between your agent and Mcp Filesystem. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.
npx -y @policylayer/intercept scan -- npx -y @ai-capabilities-suite/mcp-filesystem fs_copy_directory:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
fs_analyze_disk_usage:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The Mcp Filesystem server has 2 write tools including fs_copy_directory, fs_create_symlink. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.
12 tools across 3 categories: Execute, Read, Write. 7 are read-only. 5 can modify, create, or delete data.
One line change. Instead of running the Mcp Filesystem server directly, prefix it with Intercept: intercept -c io-github-digital-defiance-mcp-filesystem.yaml -- npx -y @@ai-capabilities-suite/mcp-filesystem. Download a pre-built policy from policylayer.com/policies/io-github-digital-defiance-mcp-filesystem and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Set budgets, approvals, and hard limits across MCP servers.
npx -y @policylayer/intercept init