AI agents call get-post-stats to retrieve information from WordPress MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves post statistics/information without modifying, deleting, or executing any operations. It is a read-only query operation that fetches data from the WordPress site. The low severity reflects that viewing post statistics poses minimal risk—it only accesses existing data without making changes or triggering external actions.
From the tool's definition Tool name 'get-post-stats' and description 'View a specific post' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get-post-stats gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WordPress MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-post-stats:
{
"version": "1",
"default": "deny",
"tools": {
"get-post-stats": {}
}
}get-post-stats 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.
View a specific post. It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for get-post-stats: 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.
get-post-stats 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 get-post-stats 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 get-post-stats. 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.
get-post-stats is provided by the WordPress MCP Server MCP server (prathammanocha/wordpress-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 WordPress MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 WordPress MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.