file_operations · MCP Demo Server MCP: Risk & Policy

WHAT IT DOES

What file_operations does on MCP Demo Server

AI agents use file_operations to create or update resources in MCP Demo Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Demo Server environment.

WHY IT NEEDS A POLICY

Why file_operations needs a policy

Although this tool includes Read operations (read, list, exists), the presence of 'write' capability elevates it to the Write category per the severity hierarchy. Write to the file system can modify or create files, which is reversible but carries significant risk if an AI agent misuses paths or overwrites critical files.

From the tool's definition Tool performs 'file system operations (read, write, list, exists)' — explicitly includes 'write' capability on the file system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

file_operations Rate-limited

file_operations stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "file_operations": {
      "limits": [
        {
          "counter": "file_operations_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Demo Server, so you can run agents against it safely.

FAQ

Questions about file_operations

What does the file_operations tool do? +

Perform file system operations (read, write, list, exists). It is categorised as a Write tool in the MCP Demo Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on file_operations? +

Register the MCP Demo Server MCP server in PolicyLayer and add a rule for file_operations: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches MCP Demo Server. Nothing to install.

What risk level is file_operations? +

file_operations is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit file_operations? +

Yes. Add a rate_limit block to the file_operations rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block file_operations completely? +

Set action: deny in the PolicyLayer policy for file_operations. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides file_operations? +

file_operations is provided by the MCP Demo Server MCP server (joohnnie/mcp-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.