List all Fizzy boards you have access to in the current account.
AI agents call fizzy_list_boards to retrieve information from Fizzy MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation—listing boards the user has access to. There are no side effects, no data modification, no code execution, and no destructive or financial operations. The blast radius of misuse is minimal; an agent listing boards cannot cause harm beyond potentially exposing information the user already has legitimate access to. This is a standard Read category tool.
From the tool's definition Tool name 'fizzy_list_boards' and description 'List all Fizzy boards you have access to in the current account' indicate a query operation that retrieves data without modifying state.
Attacks that exploit this kind of access
List all Fizzy boards you have access to in the current account. It is categorised as a Read tool in the Fizzy MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Fizzy MCP Server MCP server in PolicyLayer and add a rule for fizzy_list_boards: 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 MCP Server. Nothing to install.
fizzy_list_boards 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_list_boards 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_list_boards. 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_list_boards is provided by the Fizzy MCP Server MCP server (ryanyogan/fizzy-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 →