This record as markdown: /tools/io-github-kivanccakmak-yaver/cloud-emu-stop.md
What cloud_emu_stop does on Yaver
AI agents invoke cloud_emu_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 |
|---|---|---|---|
provider | string | Yes | |
services | string | — | |
directory | string | — |
Parameters from the server's own tool schema.
Why cloud_emu_stop is rated High
This tool executes a command to stop cloud emulators—an operational action that affects running processes. While not destructive in the data-loss sense, it terminates active services/processes, making it an Execute-class tool. The blast radius is medium because stopping emulators could disrupt local development workflows but is reversible (emulators can be restarted).
From the tool's definition Tool name 'cloud_emu_stop' combined with description 'Stop local cloud emulators' indicates this tool triggers an external operation (stopping running processes/services) whose effects depend on which emulators are running and their state.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs cloud_emu_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 cloud_emu_stop, this is the rule to start with:
cloud_emu_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every cloud_emu_stop call is checked against it from then on.
Questions about cloud_emu_stop
Stop local cloud emulators. 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.
cloud_emu_stop accepts 3 parameters: provider, services, directory. Required: provider. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for cloud_emu_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.
cloud_emu_stop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the cloud_emu_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.
Set action: deny in the PolicyLayer policy for cloud_emu_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.
cloud_emu_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.
Across the catalogue