normalize_url
Normalize a URL to a canonical form.
This record as markdown: /tools/io-tinyfn-tinyfn/normalize-url.md
What normalize_url does on TinyFn
AI agents call normalize_url to retrieve information from TinyFn 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 normalize |
sort_params | boolean | — | Sort query parameters |
lowercase_host | boolean | — | Lowercase hostname |
remove_default_port | boolean | — | Remove default port (80/443) |
remove_trailing_slash | boolean | — | Remove trailing slash from path |
Parameters from the server's own tool schema.
Why normalize_url is rated Low
URL normalization is a deterministic, read-only operation. It parses and reformats a URL string according to standard rules (e.g., lowercasing scheme/host, removing default ports, sorting query parameters) but does not retrieve data from the internet, execute arbitrary code, modify files, delete anything, or move money. It fits the 'Read' category as a query/transformation tool with no side effects.
From the tool's definition Tool name is 'normalize_url' and description states it 'Normalize[s] a URL to a canonical form.' This is a URL parsing/transformation operation with no side effects—it takes a URL as input and returns a normalized version without modifying external state,…
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs normalize_url safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TinyFn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For normalize_url, this is the rule to start with:
normalize_url 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 TinyFn, apply this rule, and every normalize_url call is checked against it from then on.
Questions about normalize_url
Normalize a URL to a canonical form. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
normalize_url accepts 5 parameters: url, sort_params, lowercase_host, remove_default_port, remove_trailing_slash. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the TinyFn MCP server in PolicyLayer and add a rule for normalize_url: 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 TinyFn. Nothing to install.
normalize_url 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 normalize_url 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 normalize_url. 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.
normalize_url is provided by the TinyFn MCP server (https://api.tinyfn.io/mcp/all/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TinyFn, and thousands of servers like it.
This server
Across the catalogue