kmp_automaton
Build a full KMP DFA transition table for streaming pattern matching.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/kmp-automaton.md
What kmp_automaton does on UnClick
AI agents invoke kmp_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 |
|---|---|---|---|
pattern | string | Yes | Pattern string (max 1000 chars) |
alphabet | string | — | Alphabet characters (default a-z) |
Parameters from the server's own tool schema.
Why kmp_automaton is rated High
KMP (Knuth-Morris-Pratt) automaton building involves algorithmic computation and data structure construction. This is an Execute category tool because it processes input (a pattern) and performs non-trivial computation to generate output (a transition table). While the operation itself is not destructive or data-modifying in a system sense, it executes a computational algorithm.
From the tool's definition Tool description states 'Build a full KMP DFA transition table for streaming pattern matching.' The verb 'build' combined with 'full KMP DFA transition table' indicates computation/code execution that constructs a data structure used for pattern matching…
Attacks that exploit this kind of access
The rule that runs kmp_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 kmp_automaton, this is the rule to start with:
kmp_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 kmp_automaton call is checked against it from then on.
Questions about kmp_automaton
Build a full KMP DFA transition table for streaming pattern matching. 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.
kmp_automaton accepts 2 parameters: pattern, alphabet. Required: pattern. 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 kmp_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.
kmp_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 kmp_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 kmp_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.
kmp_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