z_algorithm
Compute the Z-array for a string, or find pattern matches using the Z-algorithm in linear time.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/z-algorithm.md
What z_algorithm does on UnClick
AI agents invoke z_algorithm 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 |
pattern | string | — | Optional pattern to search for |
Parameters from the server's own tool schema.
Why z_algorithm is rated High
This tool performs a computational algorithm (string processing/pattern matching) on provided input. It doesn't read external data, write/modify data, or perform destructive/financial actions. It executes a computation and returns results. Severity is low as it only processes string input with no side effects or external access.
From the tool's definition 'Compute the Z-array for a string, or find pattern matches using the Z-algorithm in linear time'
Attacks that exploit this kind of access
The rule that runs z_algorithm 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 z_algorithm, this is the rule to start with:
z_algorithm 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 z_algorithm call is checked against it from then on.
Questions about z_algorithm
Compute the Z-array for a string, or find pattern matches using the Z-algorithm in linear time. 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.
z_algorithm accepts 2 parameters: text, pattern. 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 z_algorithm: 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.
z_algorithm 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 z_algorithm 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 z_algorithm. 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.
z_algorithm 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