Add a reaction to a card. Available emojis: ${REACTION_EMOJIS.join(
AI agents use fizzy_add_card_reaction to create or update resources in Fizzy Do MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fizzy Do MCP environment.
Adding a reaction modifies card state by creating a new reaction record. This is reversible (reactions can typically be removed) and has no destructive or side effects beyond the intended modification. It falls under Write category rather than Read (active modification) or Execute (no external command execution).
From the tool's definition Tool name 'fizzy_add_card_reaction' and description 'Add a reaction to a card' indicate creation/modification of reaction data on a card resource.
Attacks that exploit this kind of access
Add a reaction to a card. Available emojis: ${REACTION_EMOJIS.join(. It is categorised as a Write tool in the Fizzy Do MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fizzy Do MCP server in PolicyLayer and add a rule for fizzy_add_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_add_card_reaction is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the fizzy_add_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_add_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_add_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 →