writeFile · Readme-builder- MCP: Risk & Policy

WHAT IT DOES

What writeFile does on Readme-builder-mcp

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

WHY IT NEEDS A POLICY

Why writeFile needs a policy

The tool creates or modifies files on disk (the core purpose of writeFile), which is a Write operation. It is reversible—files can be edited or deleted afterwards. The safeguard of requiring explicit confirmation (confirm=true) mitigates risk but does not change the category. Severity is medium because unintended README overwrites could disrupt project documentation, though the impact is typically recoverable.

From the tool's definition Tool name is 'writeFile' with description stating it writes to disk ('写入磁盘') when confirm=true, and returns a preview otherwise. This is reversible file creation/modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

writeFile Rate-limited

writeFile 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": {
    "writeFile": {
      "limits": [
        {
          "counter": "writefile_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 Readme-builder-mcp, so you can run agents against it safely.

FAQ

Questions about writeFile

What does the writeFile tool do? +

confirm=true 才会写入磁盘；否则只返回预览. It is categorised as a Write tool in the Readme-builder-mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on writeFile? +

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

What risk level is writeFile? +

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

Can I rate-limit writeFile? +

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

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

writeFile is provided by the Readme-builder- MCP server (mingzhu3377/readme-builder-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.