console_machines

List every machine running a Yaver agent (local Mac/Linux/Windows + Hetzner, AWS, GCP VPSes). Hybrid view across own-hardware and cloud.

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/console-machines.md

WHAT IT DOES

What console_machines does on Yaver

AI agents call console_machines 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 console_machines is rated Low

The tool queries and returns information about machines running Yaver agents across local and cloud infrastructure. It performs no state changes, does not execute commands on machines, and does not delete or modify data. The blast radius of misuse is limited to information disclosure about infrastructure inventory, which is a low-severity Read risk.

From the tool's definition Tool description explicitly states 'List every machine' — a retrieval operation with no modification or execution. The verb 'list' is a canonical Read operation.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

console_machines Allowed

console_machines 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": {
    "console_machines": {}
  }
}

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 console_machines call is checked against it from then on.

FAQ

Questions about console_machines

What does the console_machines tool do? +

List every machine running a Yaver agent (local Mac/Linux/Windows + Hetzner, AWS, GCP VPSes). Hybrid view across own-hardware and cloud. 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 console_machines? +

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

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

Can I rate-limit console_machines? +

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

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

console_machines 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

The MCP Attack Database →

Guides

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