Inspect a local WordPress site route with a real browser. Use this after creating or changing a site to verify structure, visible content, console errors, failed requests, responsive overflow, image issues, and optional screenshots. The tool starts the site if needed and only accepts site-relativ...
AI agents invoke wpdev_site_inspect 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 launches a real browser to inspect a WordPress site route, and can also start the site if it isn't running. Triggering external processes (browser automation, starting a web server) constitutes execution of operations whose effects depend on arguments. It's not merely reading static data—it drives live browser and server processes.
From the tool's definition Inspect a local WordPress site route with a real browser... The tool starts the site if needed
Documented attack patterns abuse exactly the kind of access wpdev_site_inspect 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_site_inspect:
{
"version": "1",
"default": "deny",
"tools": {
"wpdev_site_inspect": {
"limits": [
{
"counter": "wpdev_site_inspect_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}wpdev_site_inspect 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.
Inspect a local WordPress site route with a real browser. Use this after creating or changing a site to verify structure, visible content, console errors, failed requests, responsive overflow, image issues, and optional screenshots. The tool starts the site if needed and only accepts site-relative routes. 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_site_inspect: 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_site_inspect 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_site_inspect 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_site_inspect. 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_site_inspect 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.