comment_delete

Löscht einen Kommentar

SERVERWordPress MCP Server SOURCEc-sakel/wp-mcp-server

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/c-sakel-wp-mcp-server/comment-delete.md

WHAT IT DOES

What comment_delete does on WordPress MCP Server

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

RISK

Why comment_delete is rated Critical

The tool explicitly deletes a comment, which is an irreversible destructive action. Misuse by an AI agent could result in permanent loss of user-generated content at scale.

From the tool's definition Tool name: 'comment_delete'; description translates from German as 'Deletes a comment'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs comment_delete safely

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

comment_delete Hidden

comment_delete 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": [
    "comment_delete"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about comment_delete

What does the comment_delete tool do? +

Löscht einen Kommentar. It is categorised as a Destructive tool in the WordPress MCP Server 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 comment_delete? +

Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for comment_delete: 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.

What risk level is comment_delete? +

comment_delete 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 comment_delete? +

Yes. Add a rate_limit block to the comment_delete 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 comment_delete completely? +

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

comment_delete is provided by the WordPress MCP Server MCP server (c-sakel/wp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on WordPress MCP Server, and thousands of servers like it.

This server

All 192 WordPress MCP Server tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →