bellman_ford
Find shortest paths from a source node using Bellman-Ford (handles negative edge weights).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/bellman-ford.md
What bellman_ford does on UnClick
AI agents invoke bellman_ford 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 weighted directed edges |
start | string | Yes | Start node |
target | string | — | Optional target node for path reconstruction |
Parameters from the server's own tool schema.
Why bellman_ford is rated High
This tool runs a graph algorithm (Bellman-Ford) on input data to compute shortest paths. It executes a computation rather than simply retrieving stored data or modifying persistent state.
From the tool's definition Find shortest paths from a source node using Bellman-Ford (handles negative edge weights)
Attacks that exploit this kind of access
The rule that runs bellman_ford 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 bellman_ford, this is the rule to start with:
bellman_ford 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 bellman_ford call is checked against it from then on.
Questions about bellman_ford
Find shortest paths from a source node using Bellman-Ford (handles negative edge weights). 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.
bellman_ford accepts 3 parameters: edges, start, target. Required: edges, start. 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 bellman_ford: 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.
bellman_ford 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 bellman_ford 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 bellman_ford. 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.
bellman_ford 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