network_scan_connections
Get all active network connections (TCP/UDP, states, ports, processes).
This record as markdown: /tools/aapanel-mcp/network-scan-connections.md
What network_scan_connections does on Aapanel
AI agents call network_scan_connections to retrieve information from Aapanel without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why network_scan_connections is rated Low
This tool retrieves and lists network connection metadata (protocols, states, ports, associated processes) without altering system state or data. It is purely informational. Classified as Read because it queries system state with no side effects.
From the tool's definition Tool name 'network_scan_connections' and description 'Get all active network connections (TCP/UDP, states, ports, processes)' indicate a query/retrieval operation that returns system state information without modifying anything.
Attacks that exploit this kind of access
The rule that runs network_scan_connections safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aapanel, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For network_scan_connections, this is the rule to start with:
network_scan_connections 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 Aapanel, apply this rule, and every network_scan_connections call is checked against it from then on.
Questions about network_scan_connections
Get all active network connections (TCP/UDP, states, ports, processes). It is categorised as a Read tool in the Aapanel MCP Server, which means it retrieves data without modifying state.
Register the Aapanel MCP server in PolicyLayer and add a rule for network_scan_connections: 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 Aapanel. Nothing to install.
network_scan_connections 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 network_scan_connections 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 network_scan_connections. 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.
network_scan_connections is provided by the Aapanel MCP server (nipunanirmal/aapanel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aapanel, and thousands of servers like it.
This server
Across the catalogue