get_service_key
A read tool on the Supabase MCP Server - Self-Hosted Edition MCP server.
This record as markdown: /tools/abdqum-supabase-mcp-selfhosted/get-service-key.md
What get_service_key does on Supabase MCP Server - Self-Hosted Edition
AI agents call get_service_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_service_key is rated Low
Given the name, this appears to be a Read operation that retrieves or exports a service key (likely for API access). However, with no description, there is uncertainty about whether retrieval might have initialization side-effects, permissions implications, or audit consequences.
From the tool's definition Tool name 'get_service_key' suggests retrieval of a pre-existing authentication credential; however, the description is empty, preventing definitive assessment of what the tool returns, how it operates, or what side effects it may trigger.
Attacks that exploit this kind of access
The rule that runs get_service_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_service_key, this is the rule to start with:
get_service_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_service_key call is checked against it from then on.
Questions about get_service_key
get_service_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_service_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_service_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_service_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_service_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_service_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