Delete or trash a WordPress comment.
AI agents call wordpress_delete_comment to permanently remove resources in MCP Wordpress — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of comments is a destructive operation that cannot be undone without database restoration. While the blast radius is narrower than site-wide deletion (medium-to-high rather than critical), the action is irreversible and destructive by definition. Severity is high because malicious or erroneous mass comment deletions could harm community discussions and user-generated content.
From the tool's definition Tool name and description explicitly state 'Delete or trash a WordPress comment' — the verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete or trash a WordPress comment. It is categorised as a Destructive tool in the MCP Wordpress MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Wordpress MCP server in PolicyLayer and add a rule for wordpress_delete_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_delete_comment is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the wordpress_delete_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_delete_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_delete_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 →