mcp_clean_comments

Permanently delete all spam and trashed comments

SERVERWordpress SOURCE@cavort-it-systems/wordpress-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/mcp-clean-comments.md

WHAT IT DOES

What mcp_clean_comments does on Wordpress

AI agents call mcp_clean_comments to permanently remove resources in Wordpress, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why mcp_clean_comments is rated Critical

Irreversibly removes comments without individual approval, cannot be undone.

From the tool's definition Permanently delete all spam and trashed comments

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mcp_clean_comments safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Wordpress, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mcp_clean_comments, this is the rule to start with:

mcp_clean_comments Hidden

mcp_clean_comments is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "mcp_clean_comments"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Wordpress, apply this rule, and every mcp_clean_comments call is checked against it from then on.

FAQ

Questions about mcp_clean_comments

What does the mcp_clean_comments tool do? +

Permanently delete all spam and trashed comments. It is categorised as a Destructive tool in the Wordpress MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on mcp_clean_comments? +

Register the Wordpress MCP server in PolicyLayer and add a rule for mcp_clean_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. Nothing to install.

What risk level is mcp_clean_comments? +

mcp_clean_comments is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit mcp_clean_comments? +

Yes. Add a rate_limit block to the mcp_clean_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.

How do I block mcp_clean_comments completely? +

Set action: deny in the PolicyLayer policy for mcp_clean_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.

What MCP server provides mcp_clean_comments? +

mcp_clean_comments is provided by the Wordpress MCP server (@cavort-it-systems/wordpress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Wordpress, and thousands of servers like it.

This server

All 314 Wordpress tools → Critical-risk tools on this server →

Across the catalogue

reset_mcp_runtime_metrics on 0xpdf → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →