AI agents use create-tag to create or update resources in AutoWP MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AutoWP MCP Server environment.
Creating a tag is a reversible write operation that modifies the WordPress site's taxonomy structure. While it adds new data, tags can be deleted later, making it Write rather than Destructive. The severity is medium because careless tag creation could clutter the site's taxonomy, but the impact is limited to metadata organization without affecting core content or financial operations.
From the tool's definition Tool name is 'create-tag' and description states 'Create a new WordPress tag'. This directly creates a new data entity in WordPress.
Documented attack patterns abuse exactly the kind of access create-tag gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AutoWP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create-tag:
{
"version": "1",
"default": "deny",
"tools": {
"create-tag": {
"limits": [
{
"counter": "create-tag_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create-tag 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.
Create a new WordPress tag. It is categorised as a Write tool in the AutoWP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AutoWP MCP 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 AutoWP MCP 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 AutoWP MCP Server MCP server (njengah/autowpmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AutoWP MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
47 AutoWP MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.