AI agents call wordpress_get_comments 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.
The 'get_' prefix is a standard naming convention for retrieval operations without modification. No mention of deletion, creation, modification, or execution. Comments are user-generated content that can be queried. Even with an empty description, the naming pattern and context within a content management tool set indicates this retrieves comments without side effects, classifying it as a Read operation.
From the tool's definition Tool name 'wordpress_get_comments' indicates retrieval of comment data. The empty description prevents confirmation of side effects, but the 'get_' prefix strongly suggests a read-only query operation.
Documented attack patterns abuse exactly the kind of access wordpress_get_comments 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 wordpress_get_comments:
{
"version": "1",
"default": "deny",
"tools": {
"wordpress_get_comments": {}
}
}wordpress_get_comments 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.
wordpress_get_comments. 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 wordpress_get_comments: 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.
wordpress_get_comments 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 wordpress_get_comments 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 wordpress_get_comments. 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.
wordpress_get_comments is provided by the WordPress MCP Server MCP server (raheesahmed/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 190 WordPress MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
190 WordPress MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.