write_file · Context MCP: Risk & Policy

WHAT IT DOES

What write_file does on Context

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

WHY IT NEEDS A POLICY

Why write_file needs a policy

This tool modifies the filesystem by creating or overwriting files. While reversible (files can be re-edited or deleted), it can cause significant data loss if an AI agent misuses it by overwriting critical files in a codebase without intention.

From the tool's definition Tool description explicitly states 'Create a new file or overwrite an existing file.' The name 'write_file' and description confirm this creates or modifies data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

write_file Rate-limited

write_file 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": {
    "write_file": {
      "limits": [
        {
          "counter": "write_file_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 Context, so you can run agents against it safely.

FAQ

Questions about write_file

What does the write_file tool do? +

Create a new file or overwrite an existing file. It is categorised as a Write tool in the Context MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on write_file? +

Register the Context MCP server in PolicyLayer and add a rule for write_file: 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 Context. Nothing to install.

What risk level is write_file? +

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

Can I rate-limit write_file? +

Yes. Add a rate_limit block to the write_file 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 write_file completely? +

Set action: deny in the PolicyLayer policy for write_file. 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 write_file? +

write_file is provided by the Context MCP server (vibhasdutta/context-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.