port_range_parse
Port Range Parser / IANA Classifier — Parse a comma-separated port/port-range expression into normalized ranges and classify them against IANA's well-known/registered/dynamic bands (RFC 6335).
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/port-range-parse.md
What port_range_parse does on Gateway
AI agents call port_range_parse to retrieve information from Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
expr | string | Yes | Comma-separated ports and/or ranges, e.g. '80,443,8000-9000' |
Parameters from the server's own tool schema.
Why port_range_parse is rated Low
This tool only parses and classifies port range expressions against IANA definitions. It performs no writes, executes no code, and has no side effects — purely a data transformation and lookup operation. Misuse potential is minimal.
From the tool's definition Parse a comma-separated port/port-range expression into normalized ranges and classify them against IANA's well-known/registered/dynamic bands
Attacks that exploit this kind of access
The rule that runs port_range_parse safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For port_range_parse, this is the rule to start with:
port_range_parse 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 Gateway, apply this rule, and every port_range_parse call is checked against it from then on.
Questions about port_range_parse
Port Range Parser / IANA Classifier — Parse a comma-separated port/port-range expression into normalized ranges and classify them against IANA's well-known/registered/dynamic bands (RFC 6335). It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
port_range_parse accepts 1 parameter: expr. Required: expr. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for port_range_parse: 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 Gateway. Nothing to install.
port_range_parse 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 port_range_parse 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 port_range_parse. 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.
port_range_parse is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue