This record as markdown: /tools/io-tinyfn-tinyfn/url-decode.md
What url_decode does on TinyFn
AI agents call url_decode 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 |
|---|---|---|---|
encoded | string | Yes | URL encoded string to decode |
Parameters from the server's own tool schema.
Why url_decode is rated Low
URL decoding is a reversible, read-only transformation that retrieves/extracts data from an encoded format. It does not create, modify, delete, or execute any external operations. The decoded output is data, not an action. Even if misused by an agent, it cannot cause harm beyond potentially exposing what was already encoded in the input. This is categorized as Read with low severity.
From the tool's definition Tool name 'url_decode' and description 'URL decode text' indicate a decoding operation that transforms URL-encoded strings into readable text.
Attacks that exploit this kind of access
The rule that runs url_decode 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 url_decode, this is the rule to start with:
url_decode 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 url_decode call is checked against it from then on.
Questions about url_decode
URL decode text. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
url_decode accepts 1 parameter: encoded. Required: encoded. 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 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.
url_decode 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_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.
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.
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.
More on TinyFn, and thousands of servers like it.
This server
Across the catalogue