centroid_decomposition
Compute the centroid decomposition of a tree, returning centroid parents and depths.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/centroid-decomposition.md
What centroid_decomposition does on UnClick
AI agents call centroid_decomposition to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
edges | array | Yes | Tree edges as [u, v] pairs (must be N-1 edges) |
vertex_count | number | Yes | Number of vertices (max 50,000) |
Parameters from the server's own tool schema.
Why centroid_decomposition is rated Low
Centroid decomposition is a well-known tree algorithm that analyzes structural properties. The description indicates only computation and retrieval of data (returns centroid parents and depths), with no capability to modify, delete, or execute arbitrary operations. This is a read-only algorithmic operation with minimal risk if misused by an agent.
From the tool's definition Tool computes and returns centroid decomposition properties (centroid parents and depths) of a tree structure with no mention of modification, deletion, or external side effects.
Attacks that exploit this kind of access
The rule that runs centroid_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 centroid_decomposition, this is the rule to start with:
centroid_decomposition is read-only, so it stays allowed. 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 centroid_decomposition call is checked against it from then on.
Questions about centroid_decomposition
Compute the centroid decomposition of a tree, returning centroid parents and depths. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
centroid_decomposition accepts 2 parameters: 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 centroid_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.
centroid_decomposition is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the centroid_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 centroid_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.
centroid_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.
This server
Across the catalogue