rmq_sparse
Build a sparse table for O(1) range minimum/maximum queries.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/rmq-sparse.md
What rmq_sparse does on UnClick
AI agents invoke rmq_sparse 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 |
|---|---|---|---|
mode | string | — | "min" or "max" (default min) |
values | array | Yes | Input array |
queries | array | Yes | Array of [left, right] pairs |
Parameters from the server's own tool schema.
Why rmq_sparse is rated High
This tool executes a computational algorithm (sparse table construction) rather than simply retrieving data (Read) or persisting changes (Write/Destructive). However, it appears to be a pure algorithmic utility with no external side effects, making it low severity.
From the tool's definition Tool builds a sparse table data structure for range minimum/maximum queries. The description indicates computational execution—constructing an algorithmic data structure that processes input to enable query optimization.
Attacks that exploit this kind of access
The rule that runs rmq_sparse 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 rmq_sparse, this is the rule to start with:
rmq_sparse 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 rmq_sparse call is checked against it from then on.
Questions about rmq_sparse
Build a sparse table for O(1) range minimum/maximum queries. 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.
rmq_sparse accepts 3 parameters: mode, values, queries. Required: values, 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 rmq_sparse: 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.
rmq_sparse 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 rmq_sparse 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 rmq_sparse. 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.
rmq_sparse 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