wordpress_create_tag · WordPress MCP Server MCP

WHAT IT DOES

What wordpress_create_tag does on WordPress MCP Server

AI agents use wordpress_create_tag 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.

WHY IT NEEDS A POLICY

Why wordpress_create_tag needs a policy

Creating tags modifies site data reversibly—tags can be deleted or edited later. This is a Write operation, not Read (no query), Execute (no code/command execution), Destructive (reversible), Financial (no money movement), or Other. Severity is medium because misuse could spam the taxonomy or clutter the site structure, but impact is limited to tag data and easily remediable.

From the tool's definition Tool name 'wordpress_create_tag' indicates creation of a new taxonomic element in WordPress. Context from sibling tools (wordpress_bulk_create_posts, wordpress_create_* patterns) confirms this server performs content/data creation operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_create_tag Rate-limited

wordpress_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wordpress_create_tag": {
      "limits": [
        {
          "counter": "wordpress_create_tag_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches WordPress MCP Server, so you can run agents against it safely.

FAQ

Questions about wordpress_create_tag

What does the wordpress_create_tag tool do? +

wordpress_create_tag. 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.

How do I enforce a policy on wordpress_create_tag? +

Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for wordpress_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 WordPress MCP Server. Nothing to install.

What risk level is wordpress_create_tag? +

wordpress_create_tag is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit wordpress_create_tag? +

Yes. Add a rate_limit block to the wordpress_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.

How do I block wordpress_create_tag completely? +

Set action: deny in the PolicyLayer policy for wordpress_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.

What MCP server provides wordpress_create_tag? +

wordpress_create_tag 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.