AI agents call wp_site_info 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 is a read-only query tool that retrieves and displays configuration and status information about a WordPress installation. It has no side effects, does not modify data, execute code, or perform any destructive operations. The blast radius of misuse is minimal—an attacker could learn site details but cannot directly compromise the installation from this tool alone.
From the tool's definition Tool returns informational data only: 'version, site URL, site name, active theme, and active plugin count' with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get a comprehensive overview of the WordPress installation including version, site URL, site name, active theme, and active plugin count. Great starting point for understanding a site. 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_site_info: 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_site_info 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_site_info 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_site_info. 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_site_info 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 →