preview_stop_all

Stop all preview environments.

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 00 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/preview-stop-all.md

WHAT IT DOES

What preview_stop_all does on Yaver

AI agents invoke preview_stop_all 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.

RISK

Why preview_stop_all is rated High

This tool executes a command to stop all active preview environments. While not destructive (data and configuration remain), it is Execute because it triggers external operations and has immediate side effects on running services. Severity is high because stopping all previews could disrupt development workflows and impact multiple users or projects simultaneously.

From the tool's definition Tool name 'preview_stop_all' and description 'Stop all preview environments' indicate it halts running processes/services.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

preview_stop_all Rate-limited

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

FAQ

Questions about preview_stop_all

What does the preview_stop_all tool do? +

Stop all preview environments. 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.

How do I enforce a policy on preview_stop_all? +

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

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

Can I rate-limit preview_stop_all? +

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

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

preview_stop_all 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 →