This record as markdown: /tools/io-github-kivanccakmak-yaver/network-interfaces.md
What network_interfaces does on Yaver
AI agents call network_interfaces 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 network_interfaces is rated Low
This tool retrieves information about network interfaces—a straightforward enumeration of system network state. It performs no modifications, deletions, code execution, or financial transactions.
From the tool's definition Tool name 'network_interfaces' and description 'List all network interfaces with IPs and MACs' indicates a read-only query operation that retrieves local network configuration data without modification.
Attacks that exploit this kind of access
The rule that runs network_interfaces 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 network_interfaces, this is the rule to start with:
network_interfaces 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 network_interfaces call is checked against it from then on.
Questions about network_interfaces
List all network interfaces with IPs and MACs. 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 network_interfaces: 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.
network_interfaces 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 network_interfaces 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 network_interfaces. 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.
network_interfaces 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