suffix_array_build
Build a suffix array for a string, with optional LCP (longest common prefix) array.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/suffix-array-build.md
What suffix_array_build does on UnClick
AI agents invoke suffix_array_build 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 |
|---|---|---|---|
lcp | boolean | — | Also compute the LCP array (default false) |
text | string | Yes | Input string |
Parameters from the server's own tool schema.
Why suffix_array_build is rated High
This tool executes an algorithm to build a suffix array—a standard string processing operation in computer science. While it does not retrieve data (Read), modify persistent state (Write), delete anything (Destructive), or involve financial transactions (Financial), it does trigger code execution.
From the tool's definition Tool name 'suffix_array_build' and description 'Build a suffix array for a string' indicate a computational operation that constructs a data structure from input.
Attacks that exploit this kind of access
The rule that runs suffix_array_build 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 suffix_array_build, this is the rule to start with:
suffix_array_build 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 suffix_array_build call is checked against it from then on.
Questions about suffix_array_build
Build a suffix array for a string, with optional LCP (longest common prefix) 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.
suffix_array_build accepts 2 parameters: lcp, text. 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 suffix_array_build: 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.
suffix_array_build 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 suffix_array_build 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 suffix_array_build. 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.
suffix_array_build 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