hungarian_assign
Solve the assignment problem (optimally assign N workers to N tasks) using the Hungarian algorithm.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/hungarian-assign.md
What hungarian_assign does on UnClick
AI agents invoke hungarian_assign 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 |
|---|---|---|---|
maximize | boolean | — | Maximize instead of minimize (default false) |
cost_matrix | array | Yes | NxN cost matrix |
Parameters from the server's own tool schema.
Why hungarian_assign is rated High
This tool executes an optimization algorithm (Hungarian algorithm) on provided input data to compute an optimal worker-to-task assignment. It performs computation/execution rather than simply reading stored data or writing to a data store. There are no destructive, financial, or persistent side effects evident from the description, making it a low-severity Execute tool.
From the tool's definition 'Solve the assignment problem...using the Hungarian algorithm' — runs a computational algorithm to produce an optimal assignment
Attacks that exploit this kind of access
The rule that runs hungarian_assign 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 hungarian_assign, this is the rule to start with:
hungarian_assign 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 hungarian_assign call is checked against it from then on.
Questions about hungarian_assign
Solve the assignment problem (optimally assign N workers to N tasks) using the Hungarian 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.
hungarian_assign accepts 2 parameters: maximize, cost_matrix. Required: cost_matrix. 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 hungarian_assign: 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.
hungarian_assign 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 hungarian_assign 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 hungarian_assign. 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.
hungarian_assign 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