network_scan_ports
Scan ports on a target host from the aaPanel server.
This record as markdown: /tools/aapanel-mcp/network-scan-ports.md
What network_scan_ports does on Aapanel
AI agents invoke network_scan_ports to trigger actions in Aapanel. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why network_scan_ports is rated High
Port scanning is an active network reconnaissance operation that sends probes to external hosts. It is not a passive read — it triggers outbound network activity and could be used to map attack surfaces, violate network policies, or facilitate intrusions.
From the tool's definition Scan ports on a target host from the aaPanel server
Attacks that exploit this kind of access
The rule that runs network_scan_ports 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_ports, this is the rule to start with:
network_scan_ports stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_ports call is checked against it from then on.
Questions about network_scan_ports
Scan ports on a target host from the aaPanel server. It is categorised as a Execute tool in the Aapanel MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aapanel MCP server in PolicyLayer and add a rule for network_scan_ports: 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_ports is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the network_scan_ports 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_ports. 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_ports 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.
Across the catalogue