Critical Risk →

crashes_comment_delete

Delete a single comment from a crash group via /i/crashes/delete_comment. Requires the crashes plugin. WARNING: irreversible.

Single-target operation

Part of the Countly MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

countly-mcp-server Destructive

AI agents may call crashes_comment_delete to permanently remove or destroy resources in Countly. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call crashes_comment_delete in a loop, permanently destroying resources in Countly. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

countly.yaml
tools:
  crashes_comment_delete:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Countly policy for all 127 tools.

Tool Name crashes_comment_delete
Category Destructive
MCP Server Countly MCP Server
Risk Level Critical

View all 127 tools →

Agents calling destructive-class tools like crashes_comment_delete have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

crashes_comment_delete is one of the critical-risk operations in Countly. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the crashes_comment_delete tool do? +

Delete a single comment from a crash group via /i/crashes/delete_comment. Requires the crashes plugin. WARNING: irreversible.. It is categorised as a Destructive tool in the Countly 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 crashes_comment_delete? +

Add a rule in your Intercept YAML policy under the tools section for crashes_comment_delete. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Countly MCP server.

What risk level is crashes_comment_delete? +

crashes_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 crashes_comment_delete? +

Yes. Add a rate_limit block to the crashes_comment_delete rule in your Intercept 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 crashes_comment_delete completely? +

Set action: deny in the Intercept policy for crashes_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 crashes_comment_delete? +

crashes_comment_delete is provided by the Countly MCP server (countly-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.