vibekit_deploy · Vibekit MCP: Risk & Policy

WHAT IT DOES

What vibekit_deploy does on Vibekit

AI agents invoke vibekit_deploy to trigger actions in Vibekit. 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 vibekit_deploy needs a policy

This tool triggers deployment of code to a hosting platform, which is an irreversible execution action with significant blast radius. While deployment itself may be reversible (unlike deletion), the act of deploying code to production constitutes execution of external operations whose effects depend on which repository/branch is specified.

From the tool's definition Tool description states 'Deploy a GitHub repo to VibeKit hosting.' The server description indicates it 'facilitates interaction with hosted AI agents and the execution of headless coding tasks' and enables 'control deployments.' Deploying code to hosting is a…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vibekit_deploy Rate-limited

vibekit_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": {
    "vibekit_deploy": {
      "limits": [
        {
          "counter": "vibekit_deploy_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 Vibekit, so you can run agents against it safely.

FAQ

Questions about vibekit_deploy

What does the vibekit_deploy tool do? +

Deploy a GitHub repo to VibeKit hosting. It is categorised as a Execute tool in the Vibekit MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on vibekit_deploy? +

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

What risk level is vibekit_deploy? +

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

Can I rate-limit vibekit_deploy? +

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

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

vibekit_deploy is provided by the Vibekit MCP server (vibekit-apps/vibekit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.