Low Risk

get_network_info

Get network interface information.

How to control get_network_info ↓

What get_network_info does on OODA Computer Control

AI agents call get_network_info to retrieve information from OODA Computer Control without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_network_info needs a policy

This tool retrieves and reports on network interface details (IP addresses, MAC addresses, connection status, etc.), which is a read-only operation with no side effects. It does not execute code, modify data, delete resources, or move money. While the server provides broad computer control capabilities, this specific tool is limited to information retrieval about network interfaces.

From the tool's definition Tool name 'get_network_info' and description 'Get network interface information' indicate a query operation that retrieves system network data without modification or execution of commands.

Documented attack patterns abuse exactly the kind of access get_network_info gives an agent:

How to control get_network_info

PolicyLayer is an MCP gateway — it sits between your AI agents and OODA Computer Control, and nothing reaches the server without passing your rules. This is the rule we recommend for get_network_info:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_network_info": {}
  }
}

get_network_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register OODA Computer Control — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_network_info

What does the get_network_info tool do? +

Get network interface information. It is categorised as a Read tool in the OODA Computer Control MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_network_info? +

Register the OODA Computer Control MCP server in PolicyLayer and add a rule for get_network_info: 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 OODA Computer Control. Nothing to install.

What risk level is get_network_info? +

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

Can I rate-limit get_network_info? +

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

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

get_network_info is provided by the OODA Computer Control MCP server (mnehmos/mnehmos.ooda.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OODA Computer Control tool call.

Start from OODA Computer Control, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

99 OODA Computer Control tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.