Get cards that are ready for AI work. Returns cards that are: - Golden (marked as important) - Assigned to the current user - Recently active Use this to discover what work needs to be done.
AI agents call fizzy_pm_actionable_cards to retrieve information from Fizzy Do MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a filtered list of cards based on criteria (golden status, assignment, recent activity). It performs no mutations, deletions, or external operations. The blast radius of misuse is minimal - an AI agent could only access card metadata for cards already assigned to or visible to the authenticated user, with no ability to modify state or trigger external actions.
From the tool's definition Tool name contains 'get' operation pattern; description states 'Returns cards' and 'discover what work needs to be done' - purely retrieves and queries data without modification or side effects.
Attacks that exploit this kind of access
Get cards that are ready for AI work. Returns cards that are: - Golden (marked as important) - Assigned to the current user - Recently active Use this to discover what work needs to be done. It is categorised as a Read tool in the Fizzy Do MCP MCP Server, which means it retrieves data without modifying state.
Register the Fizzy Do MCP server in PolicyLayer and add a rule for fizzy_pm_actionable_cards: 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_pm_actionable_cards is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the fizzy_pm_actionable_cards 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_pm_actionable_cards. 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_pm_actionable_cards 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 →