url_parse_normalize
URL Parser / Normalizer — Split a URL into scheme/host/port/path/query/fragment, or normalize it per RFC 3986 (lowercase host, strip default port, collapse ./.. segments).
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/url-parse-normalize.md
What url_parse_normalize does on Gateway
AI agents call url_parse_normalize 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 |
|---|---|---|---|
url | string | Yes | URL to parse or normalize (must include a scheme) |
mode | string | — | parse | normalize (default parse) |
Parameters from the server's own tool schema.
Why url_parse_normalize is rated Low
This tool only parses and normalizes URL strings into components or a canonical form. It performs no I/O, data writes, execution, or external calls — purely a stateless transformation of input data.
From the tool's definition URL Parser / Normalizer — Split a URL into scheme/host/port/path/query/fragment, or normalize it per RFC 3986 (lowercase host, strip default port, collapse ./.. segments)
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs url_parse_normalize 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 url_parse_normalize, this is the rule to start with:
url_parse_normalize 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 url_parse_normalize call is checked against it from then on.
Questions about url_parse_normalize
URL Parser / Normalizer — Split a URL into scheme/host/port/path/query/fragment, or normalize it per RFC 3986 (lowercase host, strip default port, collapse ./.. segments). It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
url_parse_normalize accepts 2 parameters: url, mode. Required: url. 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 url_parse_normalize: 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.
url_parse_normalize 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 url_parse_normalize 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 url_parse_normalize. 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.
url_parse_normalize 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