get_project_api_keys

THE RISK

Low Risk

Why get_project_api_keys needs a policy

This is a Read operation as it retrieves API keys without modifying data. However, the sensitivity is elevated to 'medium' severity because API keys are high-value secrets; if exposed to an unauthorized agent, they could be used to compromise the Supabase project.

From the tool's definition Tool name includes 'get' and description states 'Get API keys for a specific Supabase project' — this is a retrieval operation with no modification.

Documented attack patterns abuse exactly the kind of access get_project_api_keys gives an agent:

POLICY

How to control get_project_api_keys

PolicyLayer is an MCP gateway — it sits between your AI agents and Supabase MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_project_api_keys:

policy.json

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

get_project_api_keys is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Supabase MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Supabase MCP Server tools

Destructive delete_project Delete a Supabase project Write create_organization Create a new organization Write create_project Create a new Supabase project Read get_organization Get details of a specific organization Read get_project Get details of a specific Supabase project Read list_organizations List all organizations Read list_projects List all Supabase projects

All 8 Supabase MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_project_api_keys

What does the get_project_api_keys tool do? +

Get API keys for a specific Supabase project. It is categorised as a Read tool in the Supabase MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_project_api_keys? +

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

What risk level is get_project_api_keys? +

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

Can I rate-limit get_project_api_keys? +

Yes. Add a rate_limit block to the get_project_api_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_project_api_keys completely? +

Set action: deny in the PolicyLayer policy for get_project_api_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_project_api_keys? +

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

Enforce policy on every Supabase MCP Server tool call.

Start from Supabase MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →