Create a WordPress tag
AI agents use create_tag 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.
Creating a tag is a reversible write operation that adds data to the WordPress taxonomy system. It does not delete data (which would be Destructive), execute arbitrary code (Execute), transfer funds (Financial), or merely retrieve data (Read). While sibling tools include destructive operations like delete_post and delete_user, this specific tool only creates, making it Write category.
From the tool's definition Tool name is 'create_tag' and description states 'Create a WordPress tag'. This is a content creation operation that modifies WordPress data by adding a new tag taxonomy term.
Attacks that exploit this kind of access
Create a WordPress tag. 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_tag: 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_tag 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_tag 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_tag. 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_tag 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 →