This record as markdown: /tools/com-geekflare-mcp/openports.md
What openPorts does on Mcp
AI agents invoke openPorts to trigger actions in Mcp. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Target URL |
topPorts | number | — | Scan top N ports |
portRanges | string | — | Custom port ranges e.g. 80,443,1000-1010 |
Parameters from the server's own tool schema.
Why openPorts is rated High
Port scanning is an active network operation that sends packets to a remote host to probe for open ports. This is an Execute-category action (triggers external network operations). It carries high severity because an AI agent could misuse it for reconnaissance against arbitrary hosts, potentially violating terms of service or laws (e.g., unauthorized scanning).
From the tool's definition 'Scan open ports on a host' — actively performs network port scanning against an external host
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs openPorts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For openPorts, this is the rule to start with:
openPorts 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 Mcp, apply this rule, and every openPorts call is checked against it from then on.
Questions about openPorts
Scan open ports on a host. It is categorised as a Execute tool in the Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
openPorts accepts 3 parameters: url, topPorts, portRanges. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for openPorts: 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 Mcp. Nothing to install.
openPorts 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 openPorts 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 openPorts. 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.
openPorts is provided by the MCP server (@geekflare/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue