normalize_url

Normalize a URL to a canonical form.

Server TinyFn https://api.tinyfn.io/mcp/all/
Category Read
Risk class Low
Parameters 51 required

What normalize_url does on TinyFn

AI agents call normalize_url to retrieve information from TinyFn without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
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 needs a policy

Even though normalize_url only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsAccepts URL/endpoint input (url)

Questions about normalize_url

What does the normalize_url tool do? +

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.

What parameters does normalize_url accept? +

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.

How do I enforce a policy on normalize_url? +

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.

What risk level is normalize_url? +

normalize_url is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit normalize_url? +

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.

How do I block normalize_url completely? +

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.

What MCP server provides normalize_url? +

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.

// THE FULL RECORD

normalize_url is one line of TinyFn's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.