get_network_stats
Get network interface statistics: bytes sent/received, active connections summary.
This record as markdown: /tools/19miha99-system-monitor-mcp/get-network-stats.md
What get_network_stats does on Desktop Commander MCP Server
AI agents call get_network_stats to retrieve information from Desktop Commander MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_network_stats is rated Low
This tool only queries and returns network statistics (bytes sent/received, active connection counts). It performs no modifications, executions, or destructive operations. While the parent server has broad desktop control capabilities, this specific tool is limited to passive monitoring and information retrieval, making it a Read-category risk with low severity.
From the tool's definition Tool description states 'Get network interface statistics: bytes sent/received, active connections summary' — pure data retrieval with no modification or execution capability.
Attacks that exploit this kind of access
The rule that runs get_network_stats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Desktop Commander MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_network_stats, this is the rule to start with:
get_network_stats 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 Desktop Commander MCP Server, apply this rule, and every get_network_stats call is checked against it from then on.
Questions about get_network_stats
Get network interface statistics: bytes sent/received, active connections summary. It is categorised as a Read tool in the Desktop Commander MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Desktop Commander MCP Server MCP server in PolicyLayer and add a rule for get_network_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 Desktop Commander MCP Server. Nothing to install.
get_network_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 get_network_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 get_network_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.
get_network_stats is provided by the Desktop Commander MCP Server MCP server (19miha99/system-monitor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Desktop Commander MCP Server, and thousands of servers like it.
This server
Across the catalogue