Get the current Fizzy account settings including name, card count, and auto-postpone settings.
AI agents call fizzy_get_account 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 merely retrieves and displays existing account configuration data without modifying, creating, deleting, or executing any operations. It has no blast radius if invoked by an AI agent, as it cannot alter state or trigger unwanted side effects.
From the tool's definition Tool name 'fizzy_get_account' and description 'Get the current Fizzy account settings' indicate a retrieval operation with no side effects. Returns read-only data: account name, card count, and auto-postpone settings.
Attacks that exploit this kind of access
Get the current Fizzy account settings including name, card count, and auto-postpone settings. 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_get_account: 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_get_account 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_get_account 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_get_account. 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_get_account 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 →