This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/rl-encode.md
What rl_encode does on UnClick
AI agents invoke rl_encode to trigger actions in UnClick. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | Yes | Input string to encode or RLE-encoded string to decode |
decode | boolean | — | If true, decode RLE input (default false) |
Parameters from the server's own tool schema.
Why rl_encode is rated High
While string encoding/decoding is mathematically deterministic and low-impact, it qualifies as Execute rather than Read because it performs computational transformations on input. The severity is low because the blast radius is minimal—encoding/decoding strings cannot modify external state, access sensitive data, or cause harm regardless of input.
From the tool's definition Tool performs 'Run-length encode or decode' operations on strings, which involves algorithmic computation and transformation of input data. The verb 'Run' combined with encoding/decoding operations indicates code execution.
Attacks that exploit this kind of access
The rule that runs rl_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 rl_encode, this is the rule to start with:
rl_encode stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 rl_encode call is checked against it from then on.
Questions about rl_encode
Run-length encode or decode a string. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
rl_encode accepts 2 parameters: text, decode. 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 rl_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.
rl_encode is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the rl_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 rl_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.
rl_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.
Across the catalogue