Network diagnostics: interfaces, connections, listening ports, DNS, routes.
AI agents call sys_network to retrieve information from RedisNexus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and queries network configuration and status information without modifying system state or executing code. However, the severity is elevated to medium (rather than low) because network diagnostics can expose sensitive infrastructure topology, internal IP ranges, open ports, and DNS configurations that could be leveraged for reconnaissance or lateral movement in a production environment, especially…
From the tool's definition Tool performs network diagnostics and retrieval operations: 'interfaces, connections, listening ports, DNS, routes.' These are all read-only queries of system network state with no modification or execution capabilities.
Attacks that exploit this kind of access
Network diagnostics: interfaces, connections, listening ports, DNS, routes. It is categorised as a Read tool in the RedisNexus MCP Server, which means it retrieves data without modifying state.
Register the RedisNexus MCP server in PolicyLayer and add a rule for sys_network: 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 RedisNexus. Nothing to install.
sys_network 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 sys_network 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 sys_network. 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.
sys_network is provided by the RedisNexus MCP server (rajkumar-madhu/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 →