rest_api_execute

Führt eine beliebige WordPress REST API Funktion aus. Unterstützt GET, POST, PUT, PATCH und DELETE Operationen.

SERVERWordPress MCP Server SOURCEc-sakel/wp-mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/c-sakel-wp-mcp-server/rest-api-execute.md

WHAT IT DOES

What rest_api_execute does on WordPress MCP Server

AI agents invoke rest_api_execute to trigger actions in WordPress MCP Server. 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.

RISK

Why rest_api_execute is rated High

This tool allows execution of arbitrary WordPress REST API operations across all HTTP methods. While it includes destructive operations (DELETE), the primary risk is that it can execute any WordPress API function with parameters controlled by the AI agent, making outcomes dependent on arguments. This is the Execute category (code/command execution with argument-dependent effects).

From the tool's definition Tool description states it 'executes arbitrary WordPress REST API function' and supports GET, POST, PUT, PATCH and DELETE operations. The word 'beliebige' (arbitrary) is key—this permits any API call.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs rest_api_execute safely

PolicyLayer is an MCP gateway: it sits between your AI agents and WordPress MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rest_api_execute, this is the rule to start with:

rest_api_execute Rate-limited

rest_api_execute 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": {
    "rest_api_execute": {
      "limits": [
        {
          "counter": "rest_api_execute_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect WordPress MCP Server, apply this rule, and every rest_api_execute call is checked against it from then on.

FAQ

Questions about rest_api_execute

What does the rest_api_execute tool do? +

Führt eine beliebige WordPress REST API Funktion aus. Unterstützt GET, POST, PUT, PATCH und DELETE Operationen. It is categorised as a Execute tool in the WordPress MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on rest_api_execute? +

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

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

Can I rate-limit rest_api_execute? +

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

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

rest_api_execute is provided by the WordPress MCP Server MCP server (c-sakel/wp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on WordPress MCP Server, and thousands of servers like it.

This server

All 192 WordPress MCP Server tools → High-risk tools on this server →

Across the catalogue

claude_execute on Claude Bridge →execute_test_case on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →