fenwick_range
Fenwick tree with range update and range query support using two BITs.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/fenwick-range.md
What fenwick_range does on UnClick
AI agents invoke fenwick_range 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 | Initial array values |
operations | array | Yes | Array of {type, left, right, value?} operations |
Parameters from the server's own tool schema.
Why fenwick_range is rated High
A Fenwick tree (Binary Indexed Tree) implementation performs both updates and queries on an internal data structure. It modifies internal state (range update) and reads from it (range query). Since it combines both read and write/compute operations and executes algorithmic logic, Execute is the most appropriate category.
From the tool's definition Fenwick tree with range update and range query support using two BITs
Attacks that exploit this kind of access
The rule that runs fenwick_range 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 fenwick_range, this is the rule to start with:
fenwick_range 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 fenwick_range call is checked against it from then on.
Questions about fenwick_range
Fenwick tree with range update and range query support using two BITs. 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.
fenwick_range accepts 2 parameters: values, operations. Required: values, operations. 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 fenwick_range: 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.
fenwick_range 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 fenwick_range 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 fenwick_range. 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.
fenwick_range 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