Delete a comment. Only the comment creator can delete their comments.
AI agents call fizzy_delete_comment to permanently remove resources in Fizzy Do MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a comment permanently removes content that cannot be recovered. While access is restricted to the comment creator (mitigating factor for blast radius), the action itself is irreversible and destructive. This is more severe than Write (which is reversible) but less critical than Financial since it affects task management data rather than money.
From the tool's definition Tool name contains 'delete' and description states 'Delete a comment' — this is an irreversible removal of data.
Attacks that exploit this kind of access
Delete a comment. Only the comment creator can delete their comments. It is categorised as a Destructive tool in the Fizzy Do MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Fizzy Do MCP server in PolicyLayer and add a rule for fizzy_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 Fizzy Do MCP. Nothing to install.
fizzy_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 fizzy_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 fizzy_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.
fizzy_delete_comment is provided by the Fizzy Do MCP server (ryanyogan/fizzy-do-mcp). 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 →