url_decode

Decode a URL-encoded (percent-encoded) string.

SERVERUnClick SOURCE@unclick/mcp-server

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/url-decode.md

WHAT IT DOES

What url_decode does on UnClick

AI agents call url_decode to retrieve information from UnClick 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.

RISK

Why url_decode is rated Low

URL decoding is a pure data transformation utility that converts percent-encoded characters back to their original form (e.g., '%20' to space). This is a read-only operation with no capability to retrieve, write, execute, delete, or commit financial actions. It has minimal blast radius even if misused by an agent.

From the tool's definition Tool performs URL decoding (percent-decoding) of strings. Description states 'Decode a URL-encoded (percent-encoded) string' with no side effects, data modification, or external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs url_decode safely

PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, 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 Allowed

url_decode is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "url_decode": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every url_decode call is checked against it from then on.

FAQ

Questions about url_decode

What does the url_decode tool do? +

Decode a URL-encoded (percent-encoded) string. It is categorised as a Read tool in the UnClick 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 UnClick 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 UnClick. 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 UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools →

Across the catalogue

fetch_url on 0sec → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →