tsp_solve
Find a short tour visiting all cities and returning to start (traveling salesman, nearest-neighbor heuristic).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/tsp-solve.md
What tsp_solve does on UnClick
AI agents invoke tsp_solve 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 |
|---|---|---|---|
cities | array | Yes | Array of {name, x, y} city locations |
Parameters from the server's own tool schema.
Why tsp_solve is rated High
The tool executes a computational algorithm (traveling salesman problem solver) rather than simply reading or writing data. It triggers an operation whose output depends on the input arguments (the cities provided). However, it is not destructive, financial, or permanently modifying—it purely computes and returns a result.
From the tool's definition Tool description states it 'Find[s] a short tour visiting all cities and returning to start' using a computational algorithm (nearest-neighbor heuristic). This performs a computation/algorithm execution on provided input data.
Attacks that exploit this kind of access
The rule that runs tsp_solve 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 tsp_solve, this is the rule to start with:
tsp_solve 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 tsp_solve call is checked against it from then on.
Questions about tsp_solve
Find a short tour visiting all cities and returning to start (traveling salesman, nearest-neighbor heuristic). 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.
tsp_solve accepts 1 parameter: cities. Required: cities. 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 tsp_solve: 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.
tsp_solve 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 tsp_solve 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 tsp_solve. 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.
tsp_solve 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