Add a comment to a Fizzy card.
AI agents use fizzy_create_comment 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.
Creating a comment is a reversible write operation that modifies project management data. It does not execute arbitrary code, delete data irreversibly, or involve financial transactions. Severity is medium because misuse could spam cards with unwanted comments, but the blast radius is limited to single project instances and reversible via deletion.
From the tool's definition Tool description states 'Add a comment to a Fizzy card' — a create/add operation that writes new data (comment) to an existing resource (card). Similar sibling tools like fizzy_create_card, fizzy_create_board, and fizzy_create_column confirm the Write pattern.
Attacks that exploit this kind of access
Add a comment to a Fizzy card. 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_create_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_create_comment 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_create_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_create_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_create_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.
fizzy_create_comment is one line of Fizzy Do's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →