write_site_file · LocalWP MCP: Risk & Policy

WHAT IT DOES

What write_site_file does on LocalWP MCP

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

WHY IT NEEDS A POLICY

Why write_site_file needs a policy

This tool creates or modifies files within a WordPress site, which is a reversible operation. It falls under the Write category. Severity is medium because while file writes are reversible and can be undone, they could potentially modify critical site configuration files (wp-config.php, .htaccess, theme/plugin files) that might break the site or introduce vulnerabilities if an AI agent writes malicious content.

From the tool's definition Tool name is 'write_site_file' and description states 'Writes a text file inside the selected LocalWP site.' The verb 'writes' indicates creation or modification of data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

write_site_file Rate-limited

write_site_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_site_file": {
      "limits": [
        {
          "counter": "write_site_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 LocalWP MCP, so you can run agents against it safely.

FAQ

Questions about write_site_file

What does the write_site_file tool do? +

Writes a text file inside the selected LocalWP site. Requires the. It is categorised as a Write tool in the LocalWP 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 write_site_file? +

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

What risk level is write_site_file? +

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

Can I rate-limit write_site_file? +

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

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

write_site_file is provided by the LocalWP MCP server (kazimshah39/localwp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.