knapsack_solve
Solve the 0-1 knapsack problem: pick items to maximize value within a weight capacity.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/knapsack-solve.md
What knapsack_solve does on UnClick
AI agents invoke knapsack_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 |
|---|---|---|---|
items | array | Yes | Array of { name?, weight, value } objects. |
capacity | number | Yes | Maximum weight capacity (integer units, max 100000). |
Parameters from the server's own tool schema.
Why knapsack_solve is rated High
This tool runs a computational algorithm (optimization solver) rather than reading stored data, modifying persistent state, or performing financial/destructive operations. It executes a combinatorial optimization routine on provided inputs and returns a result. Severity is low because it has no external side effects — it only computes a solution locally.
From the tool's definition "Solve the 0-1 knapsack problem: pick items to maximize value within a weight capacity"
Attacks that exploit this kind of access
The rule that runs knapsack_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 knapsack_solve, this is the rule to start with:
knapsack_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 knapsack_solve call is checked against it from then on.
Questions about knapsack_solve
Solve the 0-1 knapsack problem: pick items to maximize value within a weight capacity. 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.
knapsack_solve accepts 2 parameters: items, capacity. Required: items, capacity. 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 knapsack_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.
knapsack_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 knapsack_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 knapsack_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.
knapsack_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