get_anon_key
A read tool on the Supabase MCP Server - Self-Hosted Edition MCP server.
This record as markdown: /tools/abdqum-supabase-mcp-selfhosted/get-anon-key.md
What get_anon_key does on Supabase MCP Server - Self-Hosted Edition
AI agents call get_anon_key to retrieve information from Supabase MCP Server - Self-Hosted Edition without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_anon_key is rated Low
The tool retrieves an authentication credential (anonymous key), which is a read operation with no side effects on data or system state. While credential exposure carries security implications, the tool itself performs a simple retrieval. The 'get_' prefix strongly suggests a non-destructive, non-modifying action.
From the tool's definition Tool name 'get_anon_key' indicates retrieval of an anonymous API key—a read operation that fetches credentials without modifying system state. No description provided to confirm scope, reducing confidence slightly.
Attacks that exploit this kind of access
The rule that runs get_anon_key safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Supabase MCP Server - Self-Hosted Edition, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_anon_key, this is the rule to start with:
get_anon_key is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Supabase MCP Server - Self-Hosted Edition, apply this rule, and every get_anon_key call is checked against it from then on.
Questions about get_anon_key
get_anon_key is a read tool on the Supabase MCP Server - Self-Hosted Edition MCP server. It is categorised as a Read tool in the Supabase MCP Server - Self-Hosted Edition MCP Server, which means it retrieves data without modifying state.
Register the Supabase MCP Server - Self-Hosted Edition 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 - Self-Hosted Edition. 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 - Self-Hosted Edition MCP server (abdqum/supabase-mcp-selfhosted). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Supabase MCP Server - Self-Hosted Edition, and thousands of servers like it.
Across the catalogue