Gets the API URL for a project.
AI agents call get_project_url to retrieve information from Supabase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves the API URL, which is a read operation with no side effects. API URLs are typically considered project metadata rather than sensitive secrets (distinct from API keys or credentials). The operation is informational only and carries minimal blast radius if misused by an AI agent—it merely exposes a URL that is often already public or semi-public.
From the tool's definition Tool name 'get_project_url' and description 'Gets the API URL for a project' indicates retrieval of non-sensitive project metadata. The verb 'Gets' and lack of any modification, deletion, or execution language confirm read-only behavior.
Attacks that exploit this kind of access
Gets the API URL for a project. It is categorised as a Read tool in the Supabase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Supabase MCP Server 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 MCP Server. 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 MCP server (pipethedev/supabase-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →