Check Firebase authentication status
AI agents call auth_status to retrieve information from Ice Puzzle without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only checks and returns authentication status information. It is a read-only operation with no side effects, no code execution, no data modification, and no destructive or financial impact. The low severity reflects minimal blast radius — an AI agent cannot misuse this tool to cause harm beyond potentially accessing status information it should not see, which is mitigated by proper access controls upstream.
From the tool's definition Tool name is 'auth_status' and description states 'Check Firebase authentication status' — a query operation that retrieves current authentication state without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Check Firebase authentication status. It is categorised as a Read tool in the Ice Puzzle MCP Server, which means it retrieves data without modifying state.
Register the Ice Puzzle MCP server in PolicyLayer and add a rule for auth_status: 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 Ice Puzzle. Nothing to install.
auth_status 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 auth_status 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 auth_status. 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.
auth_status is provided by the Ice Puzzle MCP server (wmoten/ice-puzzle-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 →