dinic_max_flow
Compute maximum flow in a network using Dinic's algorithm.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/dinic-max-flow.md
What dinic_max_flow does on UnClick
AI agents invoke dinic_max_flow 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 | Yes | Sink vertex |
edges | array | Yes | Edges as [u, v, capacity] triples |
source | number | Yes | Source vertex |
vertex_count | number | Yes | Number of vertices (max 10,000) |
Parameters from the server's own tool schema.
Why dinic_max_flow is rated High
This tool executes a graph algorithm (Dinic's max flow) on supplied network data. It has no side effects on external systems, data stores, or finances — it's purely computational. However, it is 'Execute' rather than 'Read' because it runs an algorithm/computation rather than retrieving existing data. Severity is low since misuse is limited to wasted compute or incorrect results.
From the tool's definition 'Compute maximum flow in a network using Dinic's algorithm' — runs a computational algorithm on provided input
Attacks that exploit this kind of access
The rule that runs dinic_max_flow 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 dinic_max_flow, this is the rule to start with:
dinic_max_flow 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 dinic_max_flow call is checked against it from then on.
Questions about dinic_max_flow
Compute maximum flow in a network using Dinic'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.
dinic_max_flow accepts 4 parameters: sink, edges, source, vertex_count. Required: sink, edges, source, 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 dinic_max_flow: 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.
dinic_max_flow 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 dinic_max_flow 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 dinic_max_flow. 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.
dinic_max_flow 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