topo_sort
Topological sort of a directed graph with cycle detection.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/topo-sort.md
What topo_sort does on UnClick
AI agents invoke topo_sort 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 [from, to] directed edge pairs. |
Parameters from the server's own tool schema.
Why topo_sort is rated High
This tool performs a graph algorithm (topological sort with cycle detection) on input data. It executes a computation rather than simply reading stored data or writing/modifying persistent state. The blast radius is low since it's a pure algorithmic operation with no apparent side effects on external systems, though the description is sparse so confidence is moderate.
From the tool's definition Topological sort of a directed graph with cycle detection
Attacks that exploit this kind of access
The rule that runs topo_sort 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 topo_sort, this is the rule to start with:
topo_sort 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 topo_sort call is checked against it from then on.
Questions about topo_sort
Topological sort of a directed graph with cycle detection. 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.
topo_sort 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 topo_sort: 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.
topo_sort 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 topo_sort 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 topo_sort. 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.
topo_sort 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