mos_algorithm
Offline range query processing using Mo's algorithm with sqrt decomposition (range sum and distinct count).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/mos-algorithm.md
What mos_algorithm does on UnClick
AI agents invoke mos_algorithm 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 |
|---|---|---|---|
array | array | Yes | Input array of numbers |
queries | array | Yes | Range queries as [l, r] pairs (0-indexed, inclusive) |
Parameters from the server's own tool schema.
Why mos_algorithm is rated High
This tool executes a computational algorithm (Mo's algorithm with sqrt decomposition) to process range queries. It runs a non-trivial computation on input data rather than simply retrieving stored data, making it Execute. Severity is medium because misuse could involve processing large or malformed datasets causing resource exhaustion, though there's no obvious destructive or financial risk.
From the tool's definition Offline range query processing using Mo's algorithm with sqrt decomposition (range sum and distinct count)
Attacks that exploit this kind of access
The rule that runs mos_algorithm 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 mos_algorithm, this is the rule to start with:
mos_algorithm 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 mos_algorithm call is checked against it from then on.
Questions about mos_algorithm
Offline range query processing using Mo's algorithm with sqrt decomposition (range sum and distinct count). 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.
mos_algorithm accepts 2 parameters: array, queries. Required: array, queries. 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 mos_algorithm: 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.
mos_algorithm 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 mos_algorithm 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 mos_algorithm. 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.
mos_algorithm 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