wordpress_add_capability · WordPress MCP Server MCP

WHAT IT DOES

What wordpress_add_capability does on WordPress MCP Server

AI agents use wordpress_add_capability 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_add_capability needs a policy

This tool modifies WordPress user capabilities, which is a Write operation (creates or modifies data reversibly). The severity is high because granting capabilities could elevate privileges and expand what users can do on the site, creating significant security implications if misapplied by an AI agent.

From the tool's definition Tool name 'wordpress_add_capability' indicates modification of user permissions/capabilities. No description provided, but the action of adding capabilities is inherently a reversible modification operation that alters access control.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_add_capability Rate-limited

wordpress_add_capability 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_add_capability": {
      "limits": [
        {
          "counter": "wordpress_add_capability_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_add_capability

What does the wordpress_add_capability tool do? +

wordpress_add_capability. 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_add_capability? +

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

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

Can I rate-limit wordpress_add_capability? +

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

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

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