cloud_emu_status

What cloud_emu_status does on Yaver

AI agents call cloud_emu_status to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameters from the server's own tool schema.

Why cloud_emu_status is rated Low

This tool retrieves and displays the status of cloud emulators, which is a read-only operation with no side effects. It queries existing state without creating, modifying, deleting, or executing code. The blast radius of misuse is minimal—an attacker could only gain visibility into what emulators are running, not affect their operation or access sensitive data through this tool alone.

From the tool's definition Tool name and description indicate a query operation: 'Show running cloud emulators across all providers' retrieves status information without modifying, deleting, or executing external operations.

Risk signalsAccepts file system path (directory)

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cloud_emu_status": {}
  }
}

Questions about cloud_emu_status