supabase_deploy

Deploy Supabase (db push or function deploy).

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 20 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/supabase-deploy.md

WHAT IT DOES

What supabase_deploy does on Yaver

AI agents invoke supabase_deploy to trigger actions in Yaver. 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.

Parameter	Type	Required	Description
`function`	string	—	Function name (deploys DB if empty)
`directory`	string	—

Parameters from the server's own tool schema.

RISK

Why supabase_deploy is rated High

Deploying to Supabase involves executing code or schema changes against a live database and function infrastructure. This is an Execute action because it runs operations whose effects depend on what is being deployed (the arguments/state). While deployment could have destructive consequences in edge cases, the primary classification is Execute since deployment itself is an orchestration of external operations.

From the tool's definition Tool name 'supabase_deploy' and description 'Deploy Supabase (db push or function deploy)' indicates execution of deployment operations that trigger external infrastructure changes.

Risk signalsAccepts file system path (directory)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs supabase_deploy safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For supabase_deploy, this is the rule to start with:

supabase_deploy Rate-limited

supabase_deploy 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": {
    "supabase_deploy": {
      "limits": [
        {
          "counter": "supabase_deploy_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every supabase_deploy call is checked against it from then on.

FAQ

Questions about supabase_deploy

What does the supabase_deploy tool do? +

Deploy Supabase (db push or function deploy). It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does supabase_deploy accept? +

supabase_deploy accepts 2 parameters: function, directory. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on supabase_deploy? +

Register the Yaver MCP server in PolicyLayer and add a rule for supabase_deploy: 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 Yaver. Nothing to install.

What risk level is supabase_deploy? +

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

Can I rate-limit supabase_deploy? +

Yes. Add a rate_limit block to the supabase_deploy 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 supabase_deploy completely? +

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

supabase_deploy is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools → High-risk tools on this server →

Across the catalogue

deploy_git_repo on cPanel MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →