graph_condensation
Compute SCC condensation of a directed graph into a DAG using Kosaraju's algorithm.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/graph-condensation.md
What graph_condensation does on UnClick
AI agents invoke graph_condensation 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 | Directed edges as [u, v] pairs (0-indexed) |
vertex_count | number | Yes | Number of vertices |
Parameters from the server's own tool schema.
Why graph_condensation is rated High
This tool executes a graph algorithm (Kosaraju's strongly connected components condensation) on input data. It performs computation rather than retrieving stored data, modifying persistent state, or causing destructive/financial effects. Severity is low because it operates on user-supplied graph data with no apparent side effects on external systems.
From the tool's definition 'Compute SCC condensation of a directed graph into a DAG using Kosaraju's algorithm' — runs a graph algorithm (computation) on provided input data
Attacks that exploit this kind of access
The rule that runs graph_condensation 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 graph_condensation, this is the rule to start with:
graph_condensation 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 graph_condensation call is checked against it from then on.
Questions about graph_condensation
Compute SCC condensation of a directed graph into a DAG using Kosaraju'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.
graph_condensation 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 graph_condensation: 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.
graph_condensation 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 graph_condensation 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 graph_condensation. 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.
graph_condensation 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