wavelet_tree
Build a wavelet tree for an integer array and answer range kth-smallest queries.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/wavelet-tree.md
What wavelet_tree does on UnClick
AI agents invoke wavelet_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 |
|---|---|---|---|
array | array | Yes | Array of integers (max 100,000) |
queries | array | — | Queries: {type:'kth', l, r, k} for kth smallest in [l, r) |
Parameters from the server's own tool schema.
Why wavelet_tree is rated High
This is a data structure construction and query tool that runs algorithmic code (wavelet tree building) to compute results. It does not retrieve existing data (Read), modify stored records (Write), delete anything (Destructive), move money (Financial), or have side effects beyond computation.
From the tool's definition Tool performs 'Build a wavelet tree' and 'answer range kth-smallest queries' — computational operations that execute an algorithm on provided data structure inputs.
Attacks that exploit this kind of access
The rule that runs wavelet_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 wavelet_tree, this is the rule to start with:
wavelet_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 wavelet_tree call is checked against it from then on.
Questions about wavelet_tree
Build a wavelet tree for an integer array and answer range kth-smallest 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.
wavelet_tree accepts 2 parameters: array, queries. Required: array. 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 wavelet_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.
wavelet_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 wavelet_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 wavelet_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.
wavelet_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