wordpress_create_term · WordPress MCP Server MCP

WHAT IT DOES

What wordpress_create_term does on WordPress MCP Server

AI agents use wordpress_create_term 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_term needs a policy

This tool creates taxonomy terms, which is a reversible Write operation. It modifies the database by adding new terms but does not delete, execute arbitrary code, or move financial resources. Severity is medium because creating malicious or spam terms could degrade site usability and SEO, but the operation is undoable (terms can be deleted).

From the tool's definition Tool name 'wordpress_create_term' indicates creation of a taxonomy term (category, tag, or custom taxonomy) in WordPress.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_create_term Rate-limited

wordpress_create_term 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_term": {
      "limits": [
        {
          "counter": "wordpress_create_term_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_term

What does the wordpress_create_term tool do? +

wordpress_create_term. 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_term? +

Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for wordpress_create_term: 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_term? +

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

Can I rate-limit wordpress_create_term? +

Yes. Add a rate_limit block to the wordpress_create_term 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_term completely? +

Set action: deny in the PolicyLayer policy for wordpress_create_term. 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_term? +

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

// THE FULL RECORD

wordpress_create_term is one line of WordPress MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →