get_edge_function
Retrieves file contents for an Edge Function in a Supabase project.
This record as markdown: /tools/supabase/get-edge-function.md
What get_edge_function does on Supabase
AI agents call get_edge_function 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 | — | |
function_slug | string | — |
Parameters from the server's own tool schema.
Why get_edge_function is rated Low
This is a read-only operation that fetches data from the Supabase project. It queries stored Edge Function code but does not execute it, deploy it, modify it, or delete it. The blast radius of misuse is limited to unauthorized information disclosure of function source code, which is a low-severity confidentiality concern.
From the tool's definition Tool retrieves file contents for an Edge Function ('Retrieves file contents'); no modification or execution occurs.
Attacks that exploit this kind of access
The rule that runs get_edge_function 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_edge_function, this is the rule to start with:
get_edge_function 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_edge_function call is checked against it from then on.
Questions about get_edge_function
Retrieves file contents for an Edge Function in a Supabase project. It is categorised as a Read tool in the Supabase MCP Server, which means it retrieves data without modifying state.
get_edge_function accepts 2 parameters: project_id, function_slug. 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_edge_function: 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_edge_function 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_edge_function 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_edge_function. 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_edge_function 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