two_sat
Solve a 2-SAT boolean satisfiability problem using implication graph and SCC.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/two-sat.md
What two_sat does on UnClick
AI agents invoke two_sat 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 |
|---|---|---|---|
clauses | array | Yes | Clauses as [a, b] pairs where positive = true, negative = negated |
variable_count | number | Yes | Number of boolean variables (1-based) |
Parameters from the server's own tool schema.
Why two_sat is rated High
This tool runs a computational algorithm (2-SAT solver using implication graph and Strongly Connected Components) on provided input. It executes logic/computation rather than reading stored data or writing/modifying persistent state. Blast radius is low since it performs only local computation with no external side effects apparent from the description.
From the tool's definition "Solve a 2-SAT boolean satisfiability problem using implication graph and SCC"
Attacks that exploit this kind of access
The rule that runs two_sat 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 two_sat, this is the rule to start with:
two_sat 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 two_sat call is checked against it from then on.
Questions about two_sat
Solve a 2-SAT boolean satisfiability problem using implication graph and SCC. 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.
two_sat accepts 2 parameters: clauses, variable_count. Required: clauses, variable_count. 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 two_sat: 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.
two_sat 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 two_sat 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 two_sat. 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.
two_sat 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