sos_dp
Sum over Subsets (SOS) dynamic programming / zeta transform on bitmasks.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/sos-dp.md
What sos_dp does on UnClick
AI agents invoke sos_dp 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 |
|---|---|---|---|
values | array | Yes | Array of values indexed by bitmask (length must be power of 2) |
direction | string | — | subset_sum or superset_sum (default: superset_sum) |
Parameters from the server's own tool schema.
Why sos_dp is rated High
This tool performs a mathematical/algorithmic computation (SOS DP / zeta transform). It executes a computation over input data (bitmasks) and returns results. It doesn't read from external sources, write/modify persistent data, or have destructive/financial effects. 'Execute' is the best fit as it runs a computational algorithm. Severity is low since it's a pure mathematical operation with no external side effects.
From the tool's definition Sum over Subsets (SOS) dynamic programming / zeta transform on bitmasks
Attacks that exploit this kind of access
The rule that runs sos_dp 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 sos_dp, this is the rule to start with:
sos_dp 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 sos_dp call is checked against it from then on.
Questions about sos_dp
Sum over Subsets (SOS) dynamic programming / zeta transform on bitmasks. 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.
sos_dp accepts 2 parameters: values, direction. Required: values. 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 sos_dp: 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.
sos_dp 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 sos_dp 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 sos_dp. 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.
sos_dp 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