sparse_table
Build a sparse table for O(1) range minimum or maximum queries on a static array.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/sparse-table.md
What sparse_table does on UnClick
AI agents invoke sparse_table 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 | — | Query mode: 'min' or 'max' (default: min) |
array | array | Yes | Array of numbers |
queries | array | — | Range queries as [left, right] pairs (inclusive) |
Parameters from the server's own tool schema.
Why sparse_table is rated High
This tool performs algorithmic computation (building a sparse table data structure) rather than simple data retrieval. It transforms input data through a specific algorithm and returns a computed result. While the operation itself is not destructive, does not modify external state, and does not perform I/O operations on real data systems, it does execute non-trivial code logic.
From the tool's definition Tool name 'sparse_table' and description 'Build a sparse table for O(1) range minimum or maximum queries on a static array' indicate a computational algorithm implementation that executes logic to construct a data structure.
Attacks that exploit this kind of access
The rule that runs sparse_table 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 sparse_table, this is the rule to start with:
sparse_table 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 sparse_table call is checked against it from then on.
Questions about sparse_table
Build a sparse table for O(1) range minimum or maximum queries on a static array. 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.
sparse_table accepts 3 parameters: mode, array, queries. Required: array. 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 sparse_table: 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.
sparse_table 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 sparse_table 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 sparse_table. 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.
sparse_table 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