simplex_solve
Solve a linear programming problem (maximize objective subject to <= constraints) using the simplex method.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/simplex-solve.md
What simplex_solve does on UnClick
AI agents invoke simplex_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 |
|---|---|---|---|
objective | array | Yes | Coefficients to maximize (e.g. [5, 4] for 5x + 4y) |
constraints | array | Yes | Array of {coeffs, bound} for <= constraints |
Parameters from the server's own tool schema.
Why simplex_solve is rated High
This tool executes a mathematical optimization algorithm (simplex method) on user-supplied data. It performs computation rather than reading stored data or writing/modifying any external state. It has no destructive, financial, or persistent side effects; the blast radius is low since it only returns a computed result.
From the tool's definition 'Solve a linear programming problem... using the simplex method' — runs a computational algorithm on provided inputs
Attacks that exploit this kind of access
The rule that runs simplex_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 simplex_solve, this is the rule to start with:
simplex_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 simplex_solve call is checked against it from then on.
Questions about simplex_solve
Solve a linear programming problem (maximize objective subject to <= constraints) using the simplex method. 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.
simplex_solve accepts 2 parameters: objective, constraints. Required: objective, constraints. 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 simplex_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.
simplex_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 simplex_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 simplex_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.
simplex_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