cloud_status

Show Yaver Cloud deployment status (containers, CPU, memory, SSL, backups).

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/cloud-status.md

WHAT IT DOES

What cloud_status does on Yaver

AI agents call cloud_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.

RISK

Why cloud_status is rated Low

This tool retrieves deployment status information without modifying infrastructure, executing commands, or triggering deployments. It is a pure informational/monitoring query with no destructive, financial, or execution capabilities. The low severity reflects that misuse would only expose system metrics, not enable harmful actions.

From the tool's definition Tool name is 'cloud_status' and description states it 'Show[s] Yaver Cloud deployment status'. The verb 'show' combined with querying status metrics (containers, CPU, memory, SSL, backups) indicates read-only retrieval with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

cloud_status Allowed

cloud_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every cloud_status call is checked against it from then on.

FAQ

Questions about cloud_status

What does the cloud_status tool do? +

Show Yaver Cloud deployment status (containers, CPU, memory, SSL, backups). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cloud_status? +

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

cloud_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cloud_status? +

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

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

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

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →