Remove a reaction from a card.
AI agents call fizzy_remove_card_reaction 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.
Removing a reaction deletes existing data (the reaction record). While low blast radius (reactions are minor social signals), the action is a deletion and cannot be passively undone, placing it in the Destructive category. Severity is low because reactions are trivial data with minimal operational impact.
From the tool's definition 'Remove a reaction from a card' — removal of data is irreversible in the sense that the specific reaction action is undone/deleted.
Attacks that exploit this kind of access
Remove a reaction from a card. 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_remove_card_reaction: 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_remove_card_reaction 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_remove_card_reaction 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_remove_card_reaction. 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_remove_card_reaction 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 →