burrows_wheeler
Compute the Burrows-Wheeler Transform (forward or inverse).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/burrows-wheeler.md
What burrows_wheeler does on UnClick
AI agents invoke burrows_wheeler 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 (or BWT output for inverse mode) |
inverse | boolean | — | If true, perform inverse BWT |
original_index | number | — | Original index (required for inverse mode) |
Parameters from the server's own tool schema.
Why burrows_wheeler is rated High
This tool performs a computational algorithm (BWT encoding/decoding) on provided input. It doesn't read from external systems, modify stored data, or have financial implications. It's a pure computation/execution of a transformation function. Severity is low as it operates only on provided input with no external side effects.
From the tool's definition 'Compute the Burrows-Wheeler Transform (forward or inverse)' — performs a computational transformation on input data
Attacks that exploit this kind of access
The rule that runs burrows_wheeler 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 burrows_wheeler, this is the rule to start with:
burrows_wheeler 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 burrows_wheeler call is checked against it from then on.
Questions about burrows_wheeler
Compute the Burrows-Wheeler Transform (forward or inverse). 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.
burrows_wheeler accepts 3 parameters: text, inverse, original_index. 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 burrows_wheeler: 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.
burrows_wheeler 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 burrows_wheeler 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 burrows_wheeler. 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.
burrows_wheeler 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