Retrieve WordPress comments with optional filtering by post, status, and search
AI agents call 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.
This tool queries and retrieves comment data from WordPress with optional filters (post, status, search) but does not create, modify, or delete any data. It has no side effects and presents minimal security risk—the worst-case scenario is exposure of comment content already visible on the site. It belongs clearly in the Read category.
From the tool's definition Tool name is 'get_comments' and description states 'Retrieve WordPress comments' with filtering options. The verb 'Retrieve' and absence of any modification language indicate a read-only operation.
Attacks that exploit this kind of access
Retrieve WordPress comments with optional filtering by post, status, and search. 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_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.
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 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 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.
get_comments is provided by the WordPress MCP Server MCP server (wolffcatskyy/wordpress-mcp). 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 →