edmonds_karp
Compute maximum flow and minimum cut in a flow network using the Edmonds-Karp (BFS-based Ford-Fulkerson) algorithm.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/edmonds-karp.md
What edmonds_karp does on UnClick
AI agents invoke edmonds_karp 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 |
|---|---|---|---|
sink | number | — | Sink vertex (default: vertices - 1) |
edges | array | Yes | Edges as [from, to, capacity] triples |
source | number | — | Source vertex (default: 0) |
vertices | number | Yes | Number of vertices |
Parameters from the server's own tool schema.
Why edmonds_karp is rated High
This tool performs a graph algorithm computation (Edmonds-Karp max-flow). It executes a mathematical/algorithmic operation on provided input data. There are no side effects on external systems, data stores, or finances — it is purely computational. However, since it runs an algorithm (Execute) rather than simply retrieving stored data (Read), Execute is the most appropriate category.
From the tool's definition 'Compute maximum flow and minimum cut in a flow network using the Edmonds-Karp (BFS-based Ford-Fulkerson) algorithm'
Attacks that exploit this kind of access
The rule that runs edmonds_karp 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 edmonds_karp, this is the rule to start with:
edmonds_karp 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 edmonds_karp call is checked against it from then on.
Questions about edmonds_karp
Compute maximum flow and minimum cut in a flow network using the Edmonds-Karp (BFS-based Ford-Fulkerson) 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.
edmonds_karp accepts 4 parameters: sink, edges, source, vertices. Required: edges, vertices. 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 edmonds_karp: 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.
edmonds_karp 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 edmonds_karp 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 edmonds_karp. 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.
edmonds_karp 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