url_decode

URL decode text.

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

What url_decode does on TinyFn

AI agents call url_decode 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
encoded string Yes URL encoded string to decode

Parameters from the server's own tool schema.

Why url_decode needs a policy

Even though url_decode 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.

Questions about url_decode

What does the url_decode tool do? +

URL decode text. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.

What parameters does url_decode accept? +

url_decode accepts 1 parameter: encoded. Required: encoded. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on url_decode? +

Register the TinyFn MCP server in PolicyLayer and add a rule for url_decode: 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 url_decode? +

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

Can I rate-limit url_decode? +

Yes. Add a rate_limit block to the url_decode 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 url_decode completely? +

Set action: deny in the PolicyLayer policy for url_decode. 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 url_decode? +

url_decode 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

url_decode 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.