AI agents call local_netstat_stats to retrieve information from Net without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries local network statistics (netstat output) to retrieve protocol counters. It reads system state without modifying data, executing commands, or causing side effects. While it runs on the local host, netstat itself is a non-destructive diagnostic utility that only collects and displays information.
From the tool's definition Tool name 'local_netstat_stats' and description 'Show network protocol statistics (TCP, UDP, ICMP counters)' indicate read-only retrieval of network diagnostic data. The verb 'show' and noun 'statistics' confirm data querying with no modification or execution.
Attacks that exploit this kind of access
Show network protocol statistics (TCP, UDP, ICMP counters). It is categorised as a Read tool in the Net MCP Server, which means it retrieves data without modifying state.
Register the Net MCP server in PolicyLayer and add a rule for local_netstat_stats: 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 Net. Nothing to install.
local_netstat_stats 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 local_netstat_stats 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 local_netstat_stats. 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.
local_netstat_stats is provided by the Net MCP server (steelcutoatmeal/net-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →