url_encode
URL-encode text (percent-encoding for query strings).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/url-encode.md
What url_encode does on UnClick
AI agents call url_encode 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 |
|---|---|---|---|
text | string | Yes | Text to URL-encode. |
Parameters from the server's own tool schema.
Why url_encode is rated Low
URL encoding is a stateless text transformation utility. It reads input text and produces encoded output without creating, modifying, deleting, or executing anything. While it's a utility that may be used in conjunction with other operations, the tool itself only performs reversible string encoding. This fits the Read category as it is a data transformation without side effects.
From the tool's definition Tool performs URL encoding of text via percent-encoding, which is a data transformation operation with no side effects, no persistence, and no external state modification.
Attacks that exploit this kind of access
The rule that runs url_encode 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_encode, this is the rule to start with:
url_encode 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 UnClick, apply this rule, and every url_encode call is checked against it from then on.
Questions about url_encode
URL-encode text (percent-encoding for query strings). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
url_encode accepts 1 parameter: text. Required: text. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for url_encode: 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.
url_encode 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_encode 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_encode. 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_encode 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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue