suffix_automaton
Build a suffix automaton for a string and count distinct substrings.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/suffix-automaton.md
What suffix_automaton does on UnClick
AI agents invoke suffix_automaton 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 (max 100,000 characters) |
Parameters from the server's own tool schema.
Why suffix_automaton is rated High
This tool executes a specific algorithm (suffix automaton construction) on string input. While it is read-only in terms of data side effects (no modifications to external state), it represents code execution that processes the input and produces computational output.
From the tool's definition Tool performs 'Build a suffix automaton' and 'count distinct substrings' - algorithmic operations that execute code logic on input data to compute and return results.
Attacks that exploit this kind of access
The rule that runs suffix_automaton 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_automaton, this is the rule to start with:
suffix_automaton 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_automaton call is checked against it from then on.
Questions about suffix_automaton
Build a suffix automaton for a string and count distinct substrings. 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_automaton 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_automaton: 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_automaton 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_automaton 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_automaton. 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_automaton 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