trie_ops
Build a trie (prefix tree) from words and perform search, prefix count, and autocomplete queries.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/trie-ops.md
What trie_ops does on UnClick
AI agents invoke trie_ops 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 |
|---|---|---|---|
words | array | Yes | Words to insert into the trie |
prefix | string | — | Prefix for autocomplete suggestions |
queries | array | — | Words to search for (exact match and prefix count) |
Parameters from the server's own tool schema.
Why trie_ops is rated High
This tool constructs an in-memory data structure (trie) and executes queries against it. It is not a pure read (it builds/transforms data), but it has no persistent side effects, no financial implications, and nothing is deleted. 'Execute' best captures the computational/transformation nature of building a structure and running operations on it.
From the tool's definition Build a trie (prefix tree) from words and perform search, prefix count, and autocomplete queries
Attacks that exploit this kind of access
The rule that runs trie_ops 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 trie_ops, this is the rule to start with:
trie_ops 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 trie_ops call is checked against it from then on.
Questions about trie_ops
Build a trie (prefix tree) from words and perform search, prefix count, and autocomplete queries. 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.
trie_ops accepts 3 parameters: words, prefix, queries. Required: words. 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 trie_ops: 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.
trie_ops 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 trie_ops 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 trie_ops. 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.
trie_ops 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