mst_find
Find the minimum spanning tree of a weighted graph using Kruskal's algorithm.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/mst-find.md
What mst_find does on UnClick
AI agents invoke mst_find 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 |
|---|---|---|---|
edges | array | Yes | Array of weighted edges |
Parameters from the server's own tool schema.
Why mst_find is rated High
This tool runs a graph algorithm (Kruskal's MST) on provided input data. It is a computational execution with no persistent side effects, data modification, or financial implications. Severity is low because it only performs an in-memory calculation on user-supplied graph data.
From the tool's definition Find the minimum spanning tree of a weighted graph using Kruskal's algorithm
Attacks that exploit this kind of access
The rule that runs mst_find 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 mst_find, this is the rule to start with:
mst_find 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 mst_find call is checked against it from then on.
Questions about mst_find
Find the minimum spanning tree of a weighted graph using Kruskal's algorithm. 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.
mst_find accepts 1 parameter: edges. Required: edges. 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 mst_find: 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.
mst_find 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 mst_find 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 mst_find. 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.
mst_find 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