cartesian_tree
Build a Cartesian tree from an array (min-heap ordered with BST on indices).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/cartesian-tree.md
What cartesian_tree does on UnClick
AI agents invoke cartesian_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 | Input array of numbers |
Parameters from the server's own tool schema.
Why cartesian_tree is rated High
While the tool performs data structure manipulation rather than retrieval (Read) or state changes to external systems (Write/Destructive), it executes code/computation logic to process an array argument. The operation depends entirely on the input argument provided.
From the tool's definition The tool 'cartesian_tree' performs a computational operation: 'Build a Cartesian tree from an array (min-heap ordered with BST on indices).' This involves executing an algorithm to transform input data into a tree structure.
Attacks that exploit this kind of access
The rule that runs cartesian_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 cartesian_tree, this is the rule to start with:
cartesian_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 cartesian_tree call is checked against it from then on.
Questions about cartesian_tree
Build a Cartesian tree from an array (min-heap ordered with BST on indices). 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.
cartesian_tree accepts 1 parameter: array. 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 cartesian_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.
cartesian_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 cartesian_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 cartesian_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.
cartesian_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