vibe_preview_stop

Stop a vibe-preview session by project. Idempotent.

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 11 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/vibe-preview-stop.md

WHAT IT DOES

What vibe_preview_stop does on Yaver

AI agents invoke vibe_preview_stop 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
`project`	string	Yes	Project name

Parameters from the server's own tool schema.

RISK

Why vibe_preview_stop is rated High

This tool triggers an external operation (terminating a vibe-preview session) whose effects depend on which project is specified as an argument. It is not merely reading data (Read), nor is it creating/modifying data reversibly in a simple sense (Write). Instead, it executes a command to stop an active process, which is characteristic of Execute category.

From the tool's definition Tool name 'vibe_preview_stop' and description 'Stop a vibe-preview session by project' indicates it terminates an active development session/process. The idempotent guarantee suggests it performs a state-changing action (stopping a running service/preview).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs vibe_preview_stop 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 vibe_preview_stop, this is the rule to start with:

vibe_preview_stop Rate-limited

vibe_preview_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": {
    "vibe_preview_stop": {
      "limits": [
        {
          "counter": "vibe_preview_stop_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 vibe_preview_stop call is checked against it from then on.

FAQ

Questions about vibe_preview_stop

What does the vibe_preview_stop tool do? +

Stop a vibe-preview session by project. Idempotent. 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 vibe_preview_stop accept? +

vibe_preview_stop accepts 1 parameter: project. Required: project. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on vibe_preview_stop? +

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

What risk level is vibe_preview_stop? +

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

Can I rate-limit vibe_preview_stop? +

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

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

vibe_preview_stop 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

stop_emba_scan on EMBA-MCP →stop_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

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