suffix_tree
Build a suffix tree (Ukkonen's algorithm) and compute distinct substrings and longest repeated substring.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/suffix-tree.md
What suffix_tree does on UnClick
AI agents invoke suffix_tree 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 text (max 10,000 chars) |
Parameters from the server's own tool schema.
Why suffix_tree is rated High
This tool executes an algorithm to process and analyze string data. It is neither a Read operation (purely retrieving existing data) nor a Write/Destructive operation (modifying persistent state), but rather an Execute category tool that runs computation on supplied arguments.
From the tool's definition Tool performs computational operations ('Build a suffix tree', 'compute distinct substrings and longest repeated substring') on provided input data using Ukkonen's algorithm.
Attacks that exploit this kind of access
The rule that runs suffix_tree 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_tree, this is the rule to start with:
suffix_tree 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_tree call is checked against it from then on.
Questions about suffix_tree
Build a suffix tree (Ukkonen's algorithm) and compute distinct substrings and longest repeated substring. 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_tree accepts 1 parameter: 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_tree: 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_tree 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_tree 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_tree. 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_tree 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