AI agents call wp_theme_file_read to retrieve information from Wp Cli without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves file contents from WordPress themes without altering them or triggering side effects. It is a pure read operation. Low severity because reading theme files does not create immediate security risk—it only exposes code/configuration data that may already be accessible through other means. Confidence is high due to explicit 'read' language and clear scope limitation to inspection.
From the tool's definition Tool name explicitly contains 'read' and description states 'Read the contents of a file in a WordPress theme' with examples of inspection use cases (template files, functions.php, style.css). No modification, deletion, or execution capability mentioned.
Attacks that exploit this kind of access
Read the contents of a file in a WordPress theme. Use this to inspect template files, functions.php, style.css, or any theme file. It is categorised as a Read tool in the Wp Cli MCP Server, which means it retrieves data without modifying state.
Register the Wp Cli MCP server in PolicyLayer and add a rule for wp_theme_file_read: 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_read is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the wp_theme_file_read 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_read. 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_read 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 →