Push a local WordPress site to a WordPress.com site. Requires WordPress.com authentication. Use wpdev_wpcom_site_list first to choose the remote site. A prior connection is not required; the CLI connects during push. Always syncs all parts of the site. This modifies the remote site, so only call ...
AI agents use wpdev_site_push 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.
The tool creates or modifies data on a remote WordPress.com site by pushing an entire local site to it. This is a Write operation rather than Destructive because the operation is reversible (the remote site can be restored from backups or overwritten again). It is not Execute because it does not run arbitrary code or commands based on user input—it performs a defined push/sync operation.
From the tool's definition Tool description states it "Push[es] a local WordPress site to a WordPress.com site" and "This modifies the remote site". The action syncs "all parts of the site" to a remote location, which constitutes creation/modification of data on the target system.
Documented attack patterns abuse exactly the kind of access wpdev_site_push 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_push:
{
"version": "1",
"default": "deny",
"tools": {
"wpdev_site_push": {
"limits": [
{
"counter": "wpdev_site_push_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}wpdev_site_push 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.
Push a local WordPress site to a WordPress.com site. Requires WordPress.com authentication. Use wpdev_wpcom_site_list first to choose the remote site. A prior connection is not required; the CLI connects during push. Always syncs all parts of the site. This modifies the remote site, so only call after the user confirms the target remote 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_push: 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_push 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_push 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_push. 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_push 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.