AI agents call wp_get_shadow_source_post 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 follows the 'wp_get_*' naming pattern used exclusively for read operations on this server. The parent server is explicitly read-only with no write, delete, or execute capabilities.
From the tool's definition Server description explicitly states 'Read-only MCP server' and tool naming convention (wp_get_*) matches other retrieval tools on the server (wp_get_post_meta, wp_get_connected_posts, wp_get_term_posts).
Documented attack patterns abuse exactly the kind of access wp_get_shadow_source_post 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_get_shadow_source_post:
{
"version": "1",
"default": "deny",
"tools": {
"wp_get_shadow_source_post": {}
}
}wp_get_shadow_source_post 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_get_shadow_source_post. 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_get_shadow_source_post: 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_get_shadow_source_post 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_get_shadow_source_post 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_get_shadow_source_post. 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_get_shadow_source_post 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.