railfence_process
Encrypt or decrypt text using the rail fence (zigzag) cipher.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/railfence-process.md
What railfence_process does on UnClick
AI agents invoke railfence_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 process. |
rails | number | — | Number of rails (default 3). |
decrypt | boolean | — | Decrypt instead of encrypt (default false). |
Parameters from the server's own tool schema.
Why railfence_process is rated High
This tool performs a computational transformation (encryption or decryption) on input text. It executes a cipher algorithm rather than simply reading/writing stored data. The blast radius is low since it only processes text passed to it and has no external side effects, data persistence, or access to external systems.
From the tool's definition Encrypt or decrypt text using the rail fence (zigzag) cipher
Attacks that exploit this kind of access
The rule that runs railfence_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 railfence_process, this is the rule to start with:
railfence_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 railfence_process call is checked against it from then on.
Questions about railfence_process
Encrypt or decrypt text using the rail fence (zigzag) cipher. 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.
railfence_process accepts 3 parameters: text, rails, decrypt. 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 railfence_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.
railfence_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 railfence_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 railfence_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.
railfence_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