unclick_encode
Encode or decode text. Supports base64, URL, HTML, and hex.
This record as markdown: /tools/creativelead-unclick/unclick-encode.md
What unclick_encode does on UnClick
AI agents call unclick_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 | — | |
operation | string | — |
Parameters from the server's own tool schema.
Why unclick_encode is rated Low
Encoding and decoding are purely computational transformations that read input and return output. No side effects, no data persistence changes, no external calls with variable effects, and no irreversible operations. This is a utility function that belongs in the Read category (general-purpose data queries/transformations with no side effects).
From the tool's definition Tool description: 'Encode or decode text. Supports base64, URL, HTML, and hex.' The tool performs reversible encoding/decoding operations on text without retrieving data from external systems, modifying persistent state, executing arbitrary code, deleting…
Attacks that exploit this kind of access
The rule that runs unclick_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 unclick_encode, this is the rule to start with:
unclick_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 unclick_encode call is checked against it from then on.
Questions about unclick_encode
Encode or decode text. Supports base64, URL, HTML, and hex. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
unclick_encode accepts 2 parameters: text, operation. 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 unclick_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.
unclick_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 unclick_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 unclick_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.
unclick_encode is provided by the UnClick MCP server (creativelead/unclick). 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