List all active users in the Fizzy account. Use user IDs from this list to assign cards.
AI agents call fizzy_list_users 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/queries user information from the Fizzy account with no side effects. It is a straightforward read operation used to enumerate users, likely to support other assignment operations.
From the tool's definition Tool name 'fizzy_list_users' and description 'List all active users in the Fizzy account' indicate a query operation that retrieves user data without modification.
Attacks that exploit this kind of access
List all active users in the Fizzy account. Use user IDs from this list to assign cards. 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_list_users: 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_list_users 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_users 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_users. 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_users 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 →