AI agents invoke wp_cli_raw to trigger actions in Wp Cli. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool permits unrestricted execution of any WP-CLI command, which is a fully-featured WordPress management interface. Given the sibling tools listed (cache flush, product creation, coupon creation, order management, user management, database operations, theme/plugin scaffolding), and the server description mentioning 'database' operations, the 'raw' execution pathway could trigger any of these…
From the tool's definition Tool name: 'wp_cli_raw'. Description: 'Execute any WP-CLI command directly'. The phrase 'Execute any WP-CLI command directly' indicates arbitrary command execution with no constraints.
Attacks that exploit this kind of access
Execute any WP-CLI command directly. It is categorised as a Execute tool in the Wp Cli MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Wp Cli MCP server in PolicyLayer and add a rule for wp_cli_raw: 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_cli_raw is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the wp_cli_raw 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_cli_raw. 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_cli_raw 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 →