Deploys a new Edge Function to a Supabase project. LLMs can use this to deploy new functions or update existing ones.
AI agents invoke deploy_edge_function to trigger actions in PostgREST. 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.
This tool triggers external operations (deployment of serverless functions) whose effects depend on the function code being deployed. While not destructive in itself (deployments are reversible via redeployment), it executes arbitrary code in a production environment, which is the hallmark of Execute category.
From the tool's definition Tool description states it "Deploys a new Edge Function to a Supabase project" and "deploy new functions or update existing ones." The word "deploys" and "update" indicate active execution of code deployment operations.
Documented attack patterns abuse exactly the kind of access deploy_edge_function gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PostgREST, and nothing reaches the server without passing your rules. This is the rule we recommend for deploy_edge_function:
{
"version": "1",
"default": "deny",
"tools": {
"deploy_edge_function": {
"limits": [
{
"counter": "deploy_edge_function_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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 PostgREST MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PostgREST 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 PostgREST. Nothing to install.
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 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 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 PostgREST MCP server (supabase/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 32 PostgREST tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
32 PostgREST tools catalogued and risk-classified — across an index of 42,500+ MCP servers.