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 MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a card is an irreversible action that removes data from the task management system. This meets the definition of Destructive—an action that cannot be undone. While access is restricted to authorized users, an AI agent with valid credentials could inadvertently or maliciously delete important cards, causing data loss.
From the tool's definition Tool name is 'fizzy_delete_card' and description states 'Delete a Fizzy card', indicating irreversible removal of data. The permission restriction (creator or admin only) does not change the destructive nature of the operation.
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 MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Fizzy MCP Server 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 MCP Server. 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 MCP Server MCP server (ryanyogan/fizzy-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 →