write_mcp_file · Homelab MCP: Risk & Policy

WHAT IT DOES

What write_mcp_file does on Homelab

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

WHY IT NEEDS A POLICY

Why write_mcp_file needs a policy

This tool creates or modifies files, which is a reversible Write operation. Severity is high because writing to MCP configuration files could alter the behavior of this homelab infrastructure server itself—affecting Docker container management, DNS settings, network configurations, or Ansible inventory.

From the tool's definition Tool explicitly performs write operation: "Write content to an MCP file. Creates parent directories if needed." The ability to create parent directories and write to arbitrary paths (absolute or relative) within the MCP directory structure creates significant…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

write_mcp_file Rate-limited

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

FAQ

Questions about write_mcp_file

What does the write_mcp_file tool do? +

Write content to an MCP file. Creates parent directories if needed. Path can be absolute or relative to MCP directory. It is categorised as a Write tool in the Homelab 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_mcp_file? +

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

What risk level is write_mcp_file? +

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

Can I rate-limit write_mcp_file? +

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

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

write_mcp_file is provided by the Homelab MCP server (myraffy/homelab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.