AI agents use wp_theme_file_write to create or update resources in Wp Cli — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wp Cli environment.
This tool creates or modifies theme files (PHP, CSS, JS) which are reversible actions (files can be edited or deleted). It does not irreversibly destroy data (not Destructive), does not move money (not Financial), and does not execute arbitrary code directly (not Execute—though modifying PHP files could affect execution).
From the tool's definition Tool description explicitly states: 'Create or overwrite a file in a WordPress theme' and 'modify CSS/JS, or create entirely new theme files.' The 'overwrite' capability combined with ability to add 'new PHP files' to a live theme represents reversible but…
Attacks that exploit this kind of access
Create or overwrite a file in a WordPress theme. Use this to edit templates, add new PHP files, modify CSS/JS, or create entirely new theme files. Directories are created automatically. It is categorised as a Write tool in the Wp Cli MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wp Cli MCP server in PolicyLayer and add a rule for wp_theme_file_write: 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 Wp Cli. Nothing to install.
wp_theme_file_write is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the wp_theme_file_write 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.
Set action: deny in the PolicyLayer policy for wp_theme_file_write. 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.
wp_theme_file_write is provided by the Wp Cli MCP server (mvtandas/wp-cli-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →