Get detailed status of a Studio site including wp-admin username as adminUsername, wp-admin password as adminPassword, phpVersion, wpVersion, and Xdebug status.
AI agents call wpdev_site_status to retrieve information from WordPress Developer MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although categorized as Read (retrieves data with no side effects), the severity is high because the tool exposes sensitive credentials (wp-admin username and password) that could be exploited by a malicious agent to gain administrative access to the WordPress site. The blast radius is significant—compromise of these credentials grants full site control.
From the tool's definition Tool returns 'wp-admin username as adminUsername, wp-admin password as adminPassword' and other sensitive configuration data. The description explicitly states it retrieves credentials and system details without modifying anything.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access wpdev_site_status 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_status:
{
"version": "1",
"default": "deny",
"tools": {
"wpdev_site_status": {}
}
}wpdev_site_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed status of a Studio site including wp-admin username as adminUsername, wp-admin password as adminPassword, phpVersion, wpVersion, and Xdebug status. It is categorised as a Read tool in the WordPress Developer MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WordPress Developer MCP Server MCP server in PolicyLayer and add a rule for wpdev_site_status: 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_status 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 wpdev_site_status 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_status. 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_status 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.