New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

web_preview_stop

Stop serving the active web preview.

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/web-preview-stop.md

What web_preview_stop does on Yaver

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

Why web_preview_stop is rated High

This tool triggers a state-change operation (stopping a running web preview server). While not destructive in the sense of deleting data, it executes a command that halts an external process. The severity is medium because stopping a development preview impacts the developer's workflow but does not delete data or cause financial harm.

From the tool's definition Tool performs an action that 'stops' an active service ('Stop serving the active web preview'), which is an external operation with side effects that cannot be instantly reversed without user re-invocation.

Questions about web_preview_stop

What does the web_preview_stop tool do? +

Stop serving the active web preview. 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 web_preview_stop? +

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

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

Can I rate-limit web_preview_stop? +

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

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

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

More on Yaver, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Yaver's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.