Delete a Fizzy card. Only the card creator or board administrators can delete cards.
AI agents call fizzy_delete_card 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.
Deletion of project data is irreversible and constitutes a destructive operation. Even with access controls (only creator or admins can delete), an AI agent with sufficient permissions could inadvertently or maliciously delete cards, destroying work items and their history. This ranks higher than Write (which is reversible) but is clearly a Destructive action per the classification rules.
From the tool's definition Tool name explicitly states 'delete' and description confirms it 'Delete a Fizzy card.' The action is irreversible — once deleted, the card and associated data are permanently removed.
Attacks that exploit this kind of access
Delete a Fizzy card. Only the card creator or board administrators can delete cards. 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_card: 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_card 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_card 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_card. 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_card 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 →