network_interfaces

List all local network interfaces with their IP addresses, subnet prefix length, and link state. Structured output from 'ip addr' (Linux) or 'ifconfig' (macOS/BSD).

SERVERMcp Nettools SOURCEaaronckj/mcp-nettools

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/aaronckj-mcp-nettools/network-interfaces.md

WHAT IT DOES

What network_interfaces does on Mcp Nettools

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

RISK

Why network_interfaces is rated Low

This tool purely retrieves and queries local network interface configuration data. It has no side effects, does not modify system state, and does not execute arbitrary commands. The underlying commands (ip addr, ifconfig) are read-only diagnostic utilities.

From the tool's definition Tool description states it 'List[s] all local network interfaces' and provides 'Structured output' from standard read-only network diagnostic commands ('ip addr' on Linux or 'ifconfig' on macOS/BSD).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs network_interfaces safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Nettools, 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 Allowed

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

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

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

FAQ

Questions about network_interfaces

What does the network_interfaces tool do? +

List all local network interfaces with their IP addresses, subnet prefix length, and link state. Structured output from 'ip addr' (Linux) or 'ifconfig' (macOS/BSD). It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on network_interfaces? +

Register the Mcp Nettools 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 Mcp Nettools. Nothing to install.

What risk level is network_interfaces? +

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

Can I rate-limit network_interfaces? +

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.

How do I block network_interfaces completely? +

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.

What MCP server provides network_interfaces? +

network_interfaces is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Nettools, and thousands of servers like it.

This server

All 235 Mcp Nettools tools →

Across the catalogue

The MCP Attack Database →

Guides

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