union_find
Perform union-find (disjoint set) operations: merge elements and query connectivity.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/union-find.md
What union_find does on UnClick
AI agents invoke union_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 |
|---|---|---|---|
unions | array | Yes | Pairs to merge |
queries | array | — | Optional pairs to check connectivity |
Parameters from the server's own tool schema.
Why union_find is rated High
The tool performs computational operations (merging elements and querying connectivity in a disjoint set data structure). It both modifies state (merge/union) and queries it, making Execute the most appropriate category. However, this appears to be an in-memory data structure operation with no persistent side effects, so severity is low.
From the tool's definition 'Perform union-find (disjoint set) operations: merge elements and query connectivity'
Attacks that exploit this kind of access
The rule that runs union_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 union_find, this is the rule to start with:
union_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 union_find call is checked against it from then on.
Questions about union_find
Perform union-find (disjoint set) operations: merge elements and query connectivity. 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.
union_find accepts 2 parameters: unions, queries. Required: unions. 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 union_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.
union_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 union_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 union_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.
union_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