Gets the anonymous API key for a project.
AI agents call get_anon_key to retrieve information from Supabase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a project credential without modifying, executing code, deleting data, or committing financial obligations. While API keys are sensitive, the 'anonymous' designation indicates it is intentionally public-facing and the tool simply retrieves it. The risk of misuse is low because anonymous keys have limited scope compared to service keys. Classification as Read is appropriate.
From the tool's definition Tool name 'get_anon_key' and description 'Gets the anonymous API key for a project' indicate a retrieval operation with no side effects. An anonymous API key is a public credential used for client-side access.
Attacks that exploit this kind of access
Gets the anonymous API key for a project. It is categorised as a Read tool in the Supabase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Supabase MCP Server MCP server in PolicyLayer and add a rule for get_anon_key: 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 Supabase MCP Server. Nothing to install.
get_anon_key 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 get_anon_key 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 get_anon_key. 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.
get_anon_key is provided by the Supabase MCP Server MCP server (pipethedev/supabase-mcp-server). 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 →