wordpress_execute_sql · WordPress MCP Server MCP

WHAT IT DOES

What wordpress_execute_sql does on WordPress MCP Server

AI agents invoke wordpress_execute_sql 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.

WHY IT NEEDS A POLICY

Why wordpress_execute_sql needs a policy

SQL execution is a classic Execute category tool because it runs database commands whose effects depend entirely on the SQL provided by the caller. With no description limiting it to read-only queries, this tool must be assumed capable of arbitrary SQL including INSERT, UPDATE, DELETE, or DROP statements.

From the tool's definition Tool name 'wordpress_execute_sql' explicitly indicates execution of SQL queries against the WordPress database. The empty description prevents verification of constraints, but the name unambiguously describes arbitrary SQL execution capability.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_execute_sql Rate-limited

wordpress_execute_sql 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_execute_sql": {
      "limits": [
        {
          "counter": "wordpress_execute_sql_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 WordPress MCP Server, so you can run agents against it safely.

FAQ

Questions about wordpress_execute_sql

What does the wordpress_execute_sql tool do? +

wordpress_execute_sql. 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 wordpress_execute_sql? +

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

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

Can I rate-limit wordpress_execute_sql? +

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

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

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