List Studio preview sites for a given path of the original Studio site.
AI agents call wpdev_preview_list 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.
This tool retrieves and displays information about existing preview sites. It has no side effects, does not modify data, and does not execute code or delete resources. The blast radius of misuse is minimal — an attacker could only discover what preview sites exist, not alter or harm them.
From the tool's definition Tool name includes 'list' and description states 'List Studio preview sites' — a straightforward enumeration/query operation with no modification, deletion, or execution capability.
Documented attack patterns abuse exactly the kind of access wpdev_preview_list 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_preview_list:
{
"version": "1",
"default": "deny",
"tools": {
"wpdev_preview_list": {}
}
}wpdev_preview_list 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.
List Studio preview sites for a given path of the original Studio site. 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_preview_list: 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_preview_list 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_preview_list 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_preview_list. 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_preview_list 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.