deploy_edge_function · Supabase MCP Server MCP

WHAT IT DOES

What deploy_edge_function does on Supabase MCP Server

AI agents invoke deploy_edge_function to trigger actions in Supabase MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why deploy_edge_function needs a policy

Deploying Edge Functions executes arbitrary code on production infrastructure with effects dependent on function implementation. While not instantly destructive or financial, deployment is a remote code execution action with significant blast radius—a misconfigured or malicious function could access data, modify state, or cause service disruption.

From the tool's definition Tool description states it 'Deploys a new Edge Function to a Supabase project' and 'can use this to deploy new functions or update existing ones.' Edge Functions are code execution units running on Supabase infrastructure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deploy_edge_function Rate-limited

deploy_edge_function stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "deploy_edge_function": {
      "limits": [
        {
          "counter": "deploy_edge_function_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Supabase MCP Server, so you can run agents against it safely.

FAQ

Questions about deploy_edge_function

What does the deploy_edge_function tool do? +

Deploys a new Edge Function to a Supabase project. LLMs can use this to deploy new functions or update existing ones. It is categorised as a Execute tool in the Supabase MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on deploy_edge_function? +

Register the Supabase MCP Server MCP server in PolicyLayer and add a rule for deploy_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 MCP Server. Nothing to install.

What risk level is deploy_edge_function? +

deploy_edge_function is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit deploy_edge_function? +

Yes. Add a rate_limit block to the deploy_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.

How do I block deploy_edge_function completely? +

Set action: deny in the PolicyLayer policy for deploy_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.

What MCP server provides deploy_edge_function? +

deploy_edge_function 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.