rle_encode_decode
Run-length encode a numeric array into runs, or decode runs back to a numeric array.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/rle-encode-decode.md
What rle_encode_decode does on UnClick
AI agents invoke rle_encode_decode 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 |
|---|---|---|---|
data | array | — | Numeric array to encode |
runs | array | — | Runs to decode |
operation | string | Yes | Operation (default encode) |
Parameters from the server's own tool schema.
Why rle_encode_decode is rated High
While the tool doesn't execute arbitrary code or shell commands, it does execute a specific computational algorithm (run-length encoding/decoding) on user-supplied input. This is a bounded, deterministic operation with no side effects, making it lower-risk within the Execute category. It doesn't permanently modify persistent state, and the blast radius of misuse is minimal.
From the tool's definition Tool performs encoding/decoding operations (rle_encode_decode) on numeric arrays, which requires running an algorithm to process and transform data.
Attacks that exploit this kind of access
The rule that runs rle_encode_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 rle_encode_decode, this is the rule to start with:
rle_encode_decode 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 rle_encode_decode call is checked against it from then on.
Questions about rle_encode_decode
Run-length encode a numeric array into runs, or decode runs back to a numeric array. 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.
rle_encode_decode accepts 3 parameters: data, runs, operation. Required: 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 rle_encode_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.
rle_encode_decode 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 rle_encode_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 rle_encode_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.
rle_encode_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.
More on UnClick, and thousands of servers like it.
Across the catalogue