Pull a WordPress.com site into a local WordPress site. Requires WordPress.com authentication. Use wpdev_wpcom_site_list first to choose the remote source. A prior connection is not required; the CLI connects during pull. Always syncs all parts of the site. This modifies the local site, so only ca...
AI agents use wpdev_site_pull 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 pulls a remote WordPress.com site into a local site, modifying the local site's content and configuration. It overwrites the local site with remote data ('Always syncs all parts of the site'), which is a significant write/overwrite operation.
From the tool's definition Pull a WordPress.com site into a local WordPress site... This modifies the local site
Documented attack patterns abuse exactly the kind of access wpdev_site_pull 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_pull:
{
"version": "1",
"default": "deny",
"tools": {
"wpdev_site_pull": {
"limits": [
{
"counter": "wpdev_site_pull_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}wpdev_site_pull 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.
Pull a WordPress.com site into a local WordPress site. Requires WordPress.com authentication. Use wpdev_wpcom_site_list first to choose the remote source. A prior connection is not required; the CLI connects during pull. Always syncs all parts of the site. This modifies the local site, so only call after the user confirms the local site and remote source. 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_pull: 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_pull 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_pull 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_pull. 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_pull 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.