runlength_process
Run-length encode or decode text (e.g. aaabbb to 3a3b).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/runlength-process.md
What runlength_process does on UnClick
AI agents invoke runlength_process 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 | Text to encode or encoded text to decode. |
decode | boolean | — | Decode instead of encode (default false). |
Parameters from the server's own tool schema.
Why runlength_process is rated High
While the tool performs a deterministic text transformation (run-length encoding/decoding) rather than arbitrary code execution, it matches the Execute category because it actively processes and transforms data through a computational operation. The operation is bounded and reversible, making it low severity—misuse would result in garbled text rather than data loss or external effects.
From the tool's definition Tool name includes 'run' and description states 'Run-length encode or decode text', indicating it processes/transforms input data through an algorithmic operation.
Attacks that exploit this kind of access
The rule that runs runlength_process 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 runlength_process, this is the rule to start with:
runlength_process 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 runlength_process call is checked against it from then on.
Questions about runlength_process
Run-length encode or decode text (e.g. aaabbb to 3a3b). 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.
runlength_process 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 runlength_process: 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.
runlength_process 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 runlength_process 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 runlength_process. 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.
runlength_process 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