Mark a Fizzy card as golden (important).
AI agents use fizzy_mark_golden 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.
This tool modifies card metadata reversibly by setting a 'golden' importance flag. It creates or updates data without deleting or executing arbitrary operations. The change is reversible (the flag can presumably be unset). Impact is limited to marking a single card's importance status, affecting only project organization/visibility within Fizzy. No external code execution, data destruction, or financial implications.
From the tool's definition Tool name 'fizzy_mark_golden' and description 'Mark a Fizzy card as golden (important)' indicate modification of a card's metadata/status flag to indicate importance.
Attacks that exploit this kind of access
Mark a Fizzy card as golden (important). 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_mark_golden: 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_mark_golden 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_mark_golden 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_mark_golden. 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_mark_golden 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 →