infra_summary
Return the managed infra summary for this device: machine profile, services, relays, networking, sharing posture, and control capabilities.
This record as markdown: /tools/io-github-kivanccakmak-yaver/infra-summary.md
What infra_summary does on Yaver
AI agents call infra_summary 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.
Why infra_summary is rated Low
This tool retrieves and reports on existing infrastructure configuration and status. It has no side effects, does not create or modify data, does not execute operations, and does not delete anything. The act of reading infrastructure summary information poses minimal risk even if misused by an AI agent, as it only exposes metadata about the device's current state.
From the tool's definition Tool description states 'Return the managed infra summary' — a retrieval operation that queries infrastructure metadata (machine profile, services, relays, networking, sharing posture, control capabilities) without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs infra_summary 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 infra_summary, this is the rule to start with:
infra_summary is read-only, so it stays allowed. 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 infra_summary call is checked against it from then on.
Questions about infra_summary
Return the managed infra summary for this device: machine profile, services, relays, networking, sharing posture, and control capabilities. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
Register the Yaver MCP server in PolicyLayer and add a rule for infra_summary: 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.
infra_summary is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the infra_summary 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 infra_summary. 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.
infra_summary 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.
This server
Across the catalogue