vibekit_exec · Vibekit MCP: Risk & Policy

WHAT IT DOES

What vibekit_exec does on Vibekit

AI agents invoke vibekit_exec 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_exec needs a policy

Shell command execution is inherently Execute category as it triggers external operations with effects determined by the command arguments. Severity is critical because: (1) shell access enables arbitrary code execution including reading sensitive files, exfiltrating data, modifying system state, or pivoting to other systems; (2) within a hosted app environment, compromise could affect multiple services; (3) there…

From the tool's definition Tool description states 'Run a shell command inside an app' — direct execution of arbitrary shell commands with unbounded capability.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vibekit_exec Rate-limited

vibekit_exec 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_exec": {
      "limits": [
        {
          "counter": "vibekit_exec_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_exec

What does the vibekit_exec tool do? +

Run a shell command inside an app. 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_exec? +

Register the Vibekit MCP server in PolicyLayer and add a rule for vibekit_exec: 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_exec? +

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

Can I rate-limit vibekit_exec? +

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

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

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