supabase_get_project
Get one Supabase project by project_ref. Read-only Management API call.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/supabase-get-project.md
What supabase_get_project does on UnClick
AI agents call supabase_get_project to retrieve information from UnClick 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 |
|---|---|---|---|
ref | string | — | Legacy alias for project_ref. |
api_key | string | — | Legacy token alias. |
project_ref | string | Yes | Supabase project ref, for example abcdefghijklmnop. |
access_token | string | — | Optional Supabase access token. Omit it to use the connected Supabase login when available. |
Parameters from the server's own tool schema.
Why supabase_get_project is rated Low
This tool retrieves project metadata from Supabase without modifying, executing operations on, or deleting data. The explicit 'Read-only' designation confirms it has no side effects and falls clearly into the Read category. Severity is low because project metadata exposure has limited blast radius unless it reveals sensitive configuration details that could be further exploited.
From the tool's definition Tool name 'supabase_get_project' and description explicitly states 'Read-only Management API call' that retrieves one Supabase project by project_ref.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs supabase_get_project safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For supabase_get_project, this is the rule to start with:
supabase_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 UnClick, apply this rule, and every supabase_get_project call is checked against it from then on.
Questions about supabase_get_project
Get one Supabase project by project_ref. Read-only Management API call. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
supabase_get_project accepts 4 parameters: ref, api_key, project_ref, access_token. Required: project_ref. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for supabase_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 UnClick. Nothing to install.
supabase_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 supabase_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 supabase_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.
supabase_get_project is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue