AI agents call wp_describe_table to retrieve information from WP Database MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool describes a table structure, which is a read-only introspection operation. Even though the tool description is empty, the server's explicit read-only designation and the naming pattern of sibling tools provide strong evidence that this is a schema inspection utility with no side effects. Blast radius is minimal—table descriptions cannot be misused to cause harm.
From the tool's definition Tool is part of 'Read-only MCP server' (stated in server description) and named 'wp_describe_table', which retrieves database schema information. Sibling tools (wp_get_*, wp_get_schema) all perform read operations.
Documented attack patterns abuse exactly the kind of access wp_describe_table 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_describe_table:
{
"version": "1",
"default": "deny",
"tools": {
"wp_describe_table": {}
}
}wp_describe_table is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
wp_describe_table. It is categorised as a Read tool in the WP Database MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WP Database MCP Server MCP server in PolicyLayer and add a rule for wp_describe_table: 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_describe_table is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the wp_describe_table 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_describe_table. 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_describe_table 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.