Create a new Studio site. If the user wants an empty/test site, create only the site and stop after sharing access details. For designed site builds, call wpdev_site_design_brief first; if it asks for input, ask only its first question and wait. Then follow its buildWorkflow and qualityBar after ...
AI agents use wpdev_site_create to create or update resources in WordPress Developer MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WordPress Developer MCP Server environment.
This tool creates new WordPress sites and configures them with pages and styling. Site creation is a reversible Write operation (a site can be deleted via wpdev_preview_delete or wpdev_fs_delete). It is not Destructive because the action is not irreversible. It is not Execute because it does not run arbitrary code or shell commands—it performs a bounded administrative operation.
From the tool's definition Tool name is 'wpdev_site_create' and description states 'Create a new Studio site' — the verb 'create' and action of instantiating a new site indicates data creation.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access wpdev_site_create 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_create:
{
"version": "1",
"default": "deny",
"tools": {
"wpdev_site_create": {
"limits": [
{
"counter": "wpdev_site_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}wpdev_site_create stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new Studio site. If the user wants an empty/test site, create only the site and stop after sharing access details. For designed site builds, call wpdev_site_design_brief first; if it asks for input, ask only its first question and wait. Then follow its buildWorkflow and qualityBar after this tool returns. If the user did not specify a custom path, you MUST use ${ STUDIO_SITE_PATH_EXAMPLE } as the default location. Use wpdev_site_list to discover all sites and their paths, to avoid using already existing paths. For designed sites, run wpdev_site_status, build real pages and visual styling, share the auto-login URL to wp-admin with the user, and suggest relevant WordPress.com, Woo, Jetpack, or official ecosystem products that fit the site. It is categorised as a Write tool in the WordPress Developer MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WordPress Developer MCP Server MCP server in PolicyLayer and add a rule for wpdev_site_create: 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_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the wpdev_site_create 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_create. 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_create 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.