get_publishable_keys

SERVERSupabase SOURCE@modelcontextprotocol/server-supabase

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade D, identity verified Pull the record →

This record as markdown: /tools/supabase/get-publishable-keys.md

WHAT IT DOES

What get_publishable_keys does on Supabase

AI agents call get_publishable_keys to retrieve information from Supabase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`project_id`	string	—

Parameters from the server's own tool schema.

RISK

Why get_publishable_keys is rated Low

This tool retrieves API keys, which are sensitive credentials. While Read operations are typically lower severity, exposing API keys allows an agent to access the Supabase project as an anonymous/public client and potentially extract data or trigger queries the project owner didn't intend.

From the tool's definition Gets all publishable API keys for a project, including legacy anon keys (JWT-based) and modern publishable keys. Retrieves authentication credentials without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_publishable_keys safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Supabase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_publishable_keys, this is the rule to start with:

get_publishable_keys Allowed

get_publishable_keys is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_publishable_keys": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Supabase, apply this rule, and every get_publishable_keys call is checked against it from then on.

FAQ

Questions about get_publishable_keys

What does the get_publishable_keys tool do? +

Gets all publishable API keys for a project, including legacy anon keys (JWT-based) and modern publishable keys (format: sb_publishable_...). Publishable keys are recommended for new applications due to better security and independent rotation. Legacy anon keys are included for compatibility, as many LLMs are pretrained on them. Disabled keys are indicated by the "disabled" field; only use keys where disabled is false or undefined. It is categorised as a Read tool in the Supabase MCP Server, which means it retrieves data without modifying state.

What parameters does get_publishable_keys accept? +

get_publishable_keys accepts 1 parameter: project_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_publishable_keys? +

Register the Supabase MCP server in PolicyLayer and add a rule for get_publishable_keys: 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. Nothing to install.

What risk level is get_publishable_keys? +

get_publishable_keys is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_publishable_keys? +

Yes. Add a rate_limit block to the get_publishable_keys 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.

How do I block get_publishable_keys completely? +

Set action: deny in the PolicyLayer policy for get_publishable_keys. 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.

What MCP server provides get_publishable_keys? +

get_publishable_keys is provided by the Supabase MCP server (@modelcontextprotocol/server-supabase). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Supabase, and thousands of servers like it.

This server

All 29 Supabase tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →