get_project_url
Gets the API URL for a project.
This record as markdown: /tools/supabase/get-project-url.md
What get_project_url does on Supabase
AI agents call get_project_url 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.
Why get_project_url is rated Low
This tool performs a read-only lookup operation that retrieves configuration information about a project. It does not create, modify, delete, or execute any operations—it simply provides a URL string. The blast radius is minimal since API URLs are typically non-sensitive configuration details that are already embedded in client applications.
From the tool's definition Tool retrieves the API URL for a project with no modification capability; the description indicates a straightforward query operation ('Gets the API URL').
Attacks that exploit this kind of access
The rule that runs get_project_url 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_url, this is the rule to start with:
get_project_url 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_url call is checked against it from then on.
Questions about get_project_url
Gets the API URL for a project. It is categorised as a Read tool in the Supabase MCP Server, which means it retrieves data without modifying state.
get_project_url accepts 1 parameter: project_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_url: 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_url 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_url 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_url. 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_url 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