create_category
AI agents use create_category 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 a category is a write operation that adds a new taxonomy term to WordPress. While reversible (can be deleted via delete_category), it modifies site structure and content organization. Severity is medium because misuse could clutter the site with unwanted categories but doesn't destroy data or cause financial harm.
From the tool's definition Tool name 'create_category' indicates creation of a new category resource in WordPress. Sibling tools show destructive operations (delete_post, delete_media, delete_category) are separately exposed, confirming this is a reversible write operation.
Attacks that exploit this kind of access
create_category. 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 create_category: 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.
create_category 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_category 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_category. 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_category is provided by the WordPress MCP Server MCP server (obot-platform/wordpress-mcp-server). 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 →