Lists all Edge Functions in a Supabase project.
AI agents call list_edge_functions 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 performs a straightforward enumeration of Edge Functions, which is a non-destructive data retrieval operation. There are no side effects, no code execution, and no data modification. The blast radius of misuse is minimal—an AI agent could at most discover what Edge Functions exist in the project, which is informational. This clearly falls under the Read category with low severity.
From the tool's definition Tool name 'list_edge_functions' and description 'Lists all Edge Functions in a Supabase project' indicate a read-only operation that retrieves and enumerates existing resources without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Lists all Edge Functions in a Supabase 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 list_edge_functions: 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.
list_edge_functions 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 list_edge_functions 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 list_edge_functions. 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.
list_edge_functions 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 →