get_network_interfaces

Get available network interfaces

SERVERCocos SOURCEcaravanglory/cocos-mcp-server

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/caravanglory-cocos-mcp-server/get-network-interfaces.md

WHAT IT DOES

What get_network_interfaces does on Cocos

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

RISK

Why get_network_interfaces is rated Low

This tool performs a read-only operation to list or retrieve information about available network interfaces on the system. It has no side effects, does not execute code or commands, does not modify data, and does not involve financial transactions.

From the tool's definition Tool name 'get_network_interfaces' and description 'Get available network interfaces' indicate a query operation that retrieves system network configuration data without modification or execution of commands.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_network_interfaces safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Cocos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_network_interfaces, this is the rule to start with:

get_network_interfaces Allowed

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

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

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

FAQ

Questions about get_network_interfaces

What does the get_network_interfaces tool do? +

Get available network interfaces. It is categorised as a Read tool in the Cocos MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_network_interfaces? +

Register the Cocos MCP server in PolicyLayer and add a rule for get_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 Cocos. Nothing to install.

What risk level is get_network_interfaces? +

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

Can I rate-limit get_network_interfaces? +

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

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

get_network_interfaces is provided by the Cocos MCP server (caravanglory/cocos-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Cocos, and thousands of servers like it.

This server

All 157 Cocos tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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