AI agents invoke wp_query to trigger actions in WP Database 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.
The tool name 'wp_query' strongly implies SQL query execution. The server description mentions 'safe SQL querying' suggesting read-only intent, but without a description we cannot confirm constraints. SQL execution tools can be misused to run expensive or sensitive queries. Since the description is empty, confidence is reduced, but Execute is the most appropriate category given the name and server context.
From the tool's definition Tool name 'wp_query' on a server described as providing 'safe SQL querying'; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access wp_query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WP Database MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for wp_query:
{
"version": "1",
"default": "deny",
"tools": {
"wp_query": {
"limits": [
{
"counter": "wp_query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}wp_query 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.
Free to start. No card required.
wp_query. It is categorised as a Execute tool in the WP Database MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the WP Database MCP Server MCP server in PolicyLayer and add a rule for wp_query: 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 WP Database MCP Server. Nothing to install.
wp_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the wp_query 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.
Set action: deny in the PolicyLayer policy for wp_query. 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.
wp_query is provided by the WP Database MCP Server MCP server (s3rgiosan/wp-db-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WP Database MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 WP Database MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.