Create a WordPress post (draft by default)
AI agents use create_post to create or update resources in WordPressMCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WordPressMCP Server environment.
This tool creates new data (posts) in a WordPress site, which is a reversible Write operation. It does not delete data (Destructive), execute arbitrary code (Execute), process financial transactions (Financial), or run shell commands. While WordPress posts can contain arbitrary content, the tool itself is constrained to post creation, not execution.
From the tool's definition Tool description states 'Create a WordPress post (draft by default)' - the verb 'Create' and action of adding new content to WordPress clearly indicates data creation.
Attacks that exploit this kind of access
Create a WordPress post (draft by default). It is categorised as a Write tool in the WordPressMCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WordPressMCP Server MCP server in PolicyLayer and add a rule for 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 WordPressMCP Server. Nothing to install.
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 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 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.
create_post is provided by the WordPressMCP Server MCP server (jahzlariosa/wordpress-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 →