get_project
Gets details for a Supabase project.
This record as markdown: /tools/supabase/get-project.md
What get_project does on Supabase
AI agents call get_project 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 |
|---|---|---|---|
id | string | — | The project ID |
Parameters from the server's own tool schema.
Why get_project is rated Low
This is a straightforward read operation that queries project metadata. It retrieves information without creating, modifying, deleting, or executing anything. The blast radius is minimal since it only exposes existing project details. Low severity because leaking project details has limited direct impact compared to tools like execute_sql or delete_branch visible on the same server.
From the tool's definition Tool name is 'get_project' and description states it 'Gets details for a Supabase project' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_project 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_project, this is the rule to start with:
get_project 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, apply this rule, and every get_project call is checked against it from then on.
Questions about get_project
Gets details for a Supabase project. It is categorised as a Read tool in the Supabase MCP Server, which means it retrieves data without modifying state.
get_project accepts 1 parameter: id. The full parameter table on this page comes from the server's own tool schema.
Register the Supabase MCP server in PolicyLayer and add a rule for get_project: 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.
get_project 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_project 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_project. 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_project 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.
More on Supabase, and thousands of servers like it.
This server
Across the catalogue