segment_tree
Build a segment tree for range queries (sum/min/max) with point updates on a mutable array.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/segment-tree.md
What segment_tree does on UnClick
AI agents invoke segment_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 |
|---|---|---|---|
values | array | Yes | Initial array of numbers |
operation | string | — | Aggregate operation (default sum) |
operations | array | — | Operations: {type:'update',index,value} or {type:'query',left,right} |
Parameters from the server's own tool schema.
Why segment_tree is rated High
This tool runs algorithmic code that modifies state (point updates on arrays). While not destructive or financial, it executes operations whose effects depend on the input data and parameters. The mutable array modifications constitute reversible state changes, elevating this beyond Read.
From the tool's definition Tool performs algorithmic operations (building segment trees, range queries, point updates) on data structures. The description indicates it executes computational logic with side effects (mutations on a mutable array via 'point updates').
Attacks that exploit this kind of access
The rule that runs segment_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 segment_tree, this is the rule to start with:
segment_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 segment_tree call is checked against it from then on.
Questions about segment_tree
Build a segment tree for range queries (sum/min/max) with point updates on a mutable array. 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.
segment_tree accepts 3 parameters: values, operation, operations. Required: values. 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 segment_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.
segment_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 segment_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 segment_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.
segment_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