Get a single WordPress comment by ID.
AI agents call wordpress_get_comment to retrieve information from MCP Wordpress without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a single comment from a WordPress site by its ID. It performs a read-only query operation with no side effects, no data modification, and no ability to delete or execute operations. The blast radius of misuse is minimal—at worst, an agent could retrieve comments it shouldn't have access to, but no data is altered or destroyed.
From the tool's definition Tool name 'wordpress_get_comment' and description 'Get a single WordPress comment by ID' indicate retrieval of existing data without modification.
Attacks that exploit this kind of access
Get a single WordPress comment by ID. It is categorised as a Read tool in the MCP Wordpress MCP Server, which means it retrieves data without modifying state.
Register the MCP Wordpress MCP server in PolicyLayer and add a rule for wordpress_get_comment: 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 MCP Wordpress. Nothing to install.
wordpress_get_comment 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_comment 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_comment. 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_comment is provided by the MCP Wordpress MCP server (crunchtools/mcp-wordpress). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →