link_cut_tree
Dynamic forest connectivity with link, cut, connected, and path sum queries using link-cut trees.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/link-cut-tree.md
What link_cut_tree does on UnClick
AI agents invoke link_cut_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 |
|---|---|---|---|
operations | array | Yes | Operations: link, cut, connected, set_value, path_sum with u, v, value fields |
vertex_count | number | Yes | Number of vertices (1-indexed) |
Parameters from the server's own tool schema.
Why link_cut_tree is rated High
The tool performs dynamic graph structure operations (link, cut, path queries) which are computational/algorithmic operations rather than simple reads. 'Link' and 'cut' modify the tree structure dynamically, making this an Execute-level operation. However, the description is vague about what data or systems are affected, lowering confidence.
From the tool's definition 'Dynamic forest connectivity with link, cut, connected, and path sum queries using link-cut trees'
Attacks that exploit this kind of access
The rule that runs link_cut_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 link_cut_tree, this is the rule to start with:
link_cut_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 link_cut_tree call is checked against it from then on.
Questions about link_cut_tree
Dynamic forest connectivity with link, cut, connected, and path sum queries using link-cut trees. 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.
link_cut_tree accepts 2 parameters: operations, vertex_count. Required: operations, 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 link_cut_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.
link_cut_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 link_cut_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 link_cut_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.
link_cut_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