wordpress_create_post
AI agents use wordpress_create_post to create or update resources in WordPress MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WordPress MCP Server environment.
Creating posts is a reversible Write operation that modifies the WordPress database by adding new content. While individual post creation is not destructive, the high severity reflects the potential blast radius in an AI context: uncontrolled post creation could flood a site with spam, inaccurate, or malicious content affecting site reputation and user experience.
From the tool's definition Tool name 'wordpress_create_post' and server context of 190+ tools for 'complete control over content' indicate this creates new post content in WordPress.
Attacks that exploit this kind of access
wordpress_create_post. It is categorised as a Write tool in the WordPress MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for wordpress_create_post: 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 MCP Server. Nothing to install.
wordpress_create_post 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 wordpress_create_post 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 wordpress_create_post. 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.
wordpress_create_post is provided by the WordPress MCP Server MCP server (tonypepperwidow123-blip/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →