wordpress_rest_request · ItchWP MCP: Risk & Policy

WHAT IT DOES

What wordpress_rest_request does on ItchWPMCP

AI agents invoke wordpress_rest_request to trigger actions in ItchWPMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why wordpress_rest_request needs a policy

This tool is a generic escape hatch that can issue any HTTP method against the WordPress REST API. While GET requests are read-only, non-GET requests (POST, PUT, PATCH, DELETE) can create, modify, or delete any WordPress content, install plugins, manage users, or perform other destructive/write operations.

From the tool's definition 'Advanced escape hatch for WordPress REST API calls. Non-GET requests obey write guards.' — arbitrary REST API calls including POST, PUT, PATCH, DELETE methods

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_rest_request Rate-limited

wordpress_rest_request stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_rest_request": {
      "limits": [
        {
          "counter": "wordpress_rest_request_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about wordpress_rest_request

What does the wordpress_rest_request tool do? +

Advanced escape hatch for WordPress REST API calls. Non-GET requests obey write guards. It is categorised as a Execute tool in the ItchWPMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wordpress_rest_request? +

Register the ItchWP MCP server in PolicyLayer and add a rule for wordpress_rest_request: 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 ItchWPMCP. Nothing to install.

What risk level is wordpress_rest_request? +

wordpress_rest_request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit wordpress_rest_request? +

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

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

wordpress_rest_request is provided by the ItchWP MCP server (manofsadness/itchwpmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.