Deploys an Edge Function to a Supabase project. If the function already exists, this will create a new version. Example: import "jsr:@supabase/functions-js/edge-runtime.d.ts"; Deno.serve(async (req: Request) => { const data = { message: "Hello there!" }; return new Response(JSON.st...
Accepts raw HTML/template content (files[].content)
Part of the Supabase Godmode MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke deploy_edge_function to trigger processes or run actions in Supabase Godmode. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
deploy_edge_function can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
deploy_edge_function:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Supabase Godmode policy for all 29 tools.
Agents calling execute-class tools like deploy_edge_function have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
deploy_edge_function is one of the high-risk operations in Supabase Godmode. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Deploys an Edge Function to a Supabase project. If the function already exists, this will create a new version. Example: import "jsr:@supabase/functions-js/edge-runtime.d.ts"; Deno.serve(async (req: Request) => { const data = { message: "Hello there!" }; return new Response(JSON.stringify(data), { headers: { 'Content-Type': 'application/json', 'Connection': 'keep-alive' } }); });. It is categorised as a Execute tool in the Supabase Godmode MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for deploy_edge_function. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Supabase Godmode MCP server.
deploy_edge_function is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the deploy_edge_function rule in your Intercept 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 Intercept 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.
deploy_edge_function is provided by the Supabase Godmode MCP server (ubiq/supabase-godmode). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept