Run WP-CLI commands on a Studio site. Use deliberately because WP-CLI can be slower than file reads/writes. Prefer compact output with --format=json and --fields for list commands, and avoid many tiny exploratory calls when one purposeful command is enough. Examples:
AI agents invoke wpdev_wp to trigger actions in WordPress Developer MCP Server. 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 allows execution of arbitrary WP-CLI commands whose effects depend entirely on the arguments provided. WP-CLI commands can perform destructive operations (delete posts, drop database tables), financial transactions (if plugins enable payments), writes (modify settings, create users), and reads (query data). However, the primary capability is code/command execution on a WordPress system.
From the tool's definition Tool explicitly enables 'Run WP-CLI commands' on a WordPress site. WP-CLI is a command-line interface that can execute arbitrary operations on WordPress installations, including creating users, modifying settings, installing plugins, executing code, and…
Documented attack patterns abuse exactly the kind of access wpdev_wp gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WordPress Developer MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for wpdev_wp:
{
"version": "1",
"default": "deny",
"tools": {
"wpdev_wp": {
"limits": [
{
"counter": "wpdev_wp_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}wpdev_wp stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Run WP-CLI commands on a Studio site. Use deliberately because WP-CLI can be slower than file reads/writes. Prefer compact output with --format=json and --fields for list commands, and avoid many tiny exploratory calls when one purposeful command is enough. Examples:. It is categorised as a Execute tool in the WordPress Developer MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the WordPress Developer MCP Server MCP server in PolicyLayer and add a rule for wpdev_wp: 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 WordPress Developer MCP Server. Nothing to install.
wpdev_wp 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 wpdev_wp 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 wpdev_wp. 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.
wpdev_wp is provided by the WordPress Developer MCP Server MCP server (nightnei/wordpress-developer-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 25 WordPress Developer MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
25 WordPress Developer MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.