delete_comment

THE RISK

Critical Risk

Why delete_comment needs a policy

Deletion of comments is a destructive operation that removes data from the feedback management system. Even though the description notes a 'soft delete if has replies' (suggesting some preservation logic), the primary action is deletion—removal of user-generated content that cannot be easily restored without admin intervention. This falls under the Destructive category.

From the tool's definition Tool name is 'delete_comment' and description states 'Delete a comment'. The verb 'delete' combined with the operational effect of removing a comment constitutes an irreversible or difficult-to-reverse action on customer feedback data.

Documented attack patterns abuse exactly the kind of access delete_comment gives an agent:

POLICY

How to control delete_comment

PolicyLayer is an MCP gateway — it sits between your AI agents and Featurebase MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_comment:

policy.json

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

delete_comment disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Featurebase MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Featurebase MCP Server tools

Destructive delete_post Delete a post permanently Write add_upvoter Add an upvoter to a post Write create_comment Create a new comment or reply Write create_post Create a new post Write update_comment Update an existing comment Write update_post Update an existing post Read get_comments Get comments for a post or changelog. Available fields: ${commentModel}, replies(${comment Read get_post_upvoters Get list of users who upvoted a post

All 12 Featurebase MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Featurebase MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_comment

What does the delete_comment tool do? +

Delete a comment (soft delete if has replies). It is categorised as a Destructive tool in the Featurebase 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 delete_comment? +

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

What risk level is delete_comment? +

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

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

How do I block delete_comment completely? +

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

What MCP server provides delete_comment? +

delete_comment is provided by the Featurebase MCP Server MCP server (marcinwyszynski/featurebase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Featurebase MCP Server tool call.

Start from Featurebase MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →