vibekit_agent_stop · Vibekit MCP: Risk & Policy

WHAT IT DOES

What vibekit_agent_stop does on Vibekit

AI agents invoke vibekit_agent_stop 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_agent_stop needs a policy

This tool executes a command that halts an active process on remote infrastructure. While not immediately destructive (the agent is paused, not permanently deleted), it is an Execute category action because it triggers an external operation with real-world side effects.

From the tool's definition Tool description: 'Stop a currently running agent request.' This performs an action that triggers an external operation (stopping a running process/agent) whose effects depend on which agent is targeted.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vibekit_agent_stop Rate-limited

vibekit_agent_stop 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_agent_stop": {
      "limits": [
        {
          "counter": "vibekit_agent_stop_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_agent_stop

What does the vibekit_agent_stop tool do? +

Stop a currently running agent request. 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_agent_stop? +

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

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

Can I rate-limit vibekit_agent_stop? +

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

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

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