heavy_light_decomposition
Perform heavy-light decomposition of a tree for efficient path queries.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/heavy-light-decomposition.md
What heavy_light_decomposition does on UnClick
AI agents invoke heavy_light_decomposition 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 |
|---|---|---|---|
root | number | — | Root vertex (default 0) |
edges | array | Yes | Edges as [u, v] pairs (0-indexed) |
vertex_count | number | Yes | Number of vertices |
Parameters from the server's own tool schema.
Why heavy_light_decomposition is rated High
This tool performs a computational operation (heavy-light decomposition) on a tree structure to enable path queries. It executes an algorithm rather than simply reading stored data or writing/modifying persistent data. The blast radius is medium since misuse could produce incorrect query results or consume significant compute resources, but it doesn't appear to modify persistent data or have financial implications.
From the tool's definition 'Perform heavy-light decomposition of a tree for efficient path queries' — executes a computational algorithm/query operation on tree data structures
Attacks that exploit this kind of access
The rule that runs heavy_light_decomposition 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 heavy_light_decomposition, this is the rule to start with:
heavy_light_decomposition 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 heavy_light_decomposition call is checked against it from then on.
Questions about heavy_light_decomposition
Perform heavy-light decomposition of a tree for efficient path 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.
heavy_light_decomposition accepts 3 parameters: root, edges, vertex_count. Required: edges, vertex_count. 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 heavy_light_decomposition: 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.
heavy_light_decomposition 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 heavy_light_decomposition 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 heavy_light_decomposition. 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.
heavy_light_decomposition 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