fenwick_2d
2D Fenwick tree for point updates and rectangle sum queries.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/fenwick-2d.md
What fenwick_2d does on UnClick
AI agents invoke fenwick_2d 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 |
|---|---|---|---|
cols | number | Yes | Number of columns |
rows | number | Yes | Number of rows |
operations | array | Yes | Array of {type, row, col, row2?, col2?, value?} operations |
Parameters from the server's own tool schema.
Why fenwick_2d is rated High
This tool performs both data updates ('point updates') and queries ('rectangle sum queries') on an in-memory data structure. The 'point updates' aspect makes it more than a pure read, but since it operates on an ephemeral/local data structure (a Fenwick tree) rather than persisting to external storage, it is best classified as Execute (running a computational operation).
From the tool's definition 2D Fenwick tree for point updates and rectangle sum queries
Attacks that exploit this kind of access
The rule that runs fenwick_2d 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_2d, this is the rule to start with:
fenwick_2d 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_2d call is checked against it from then on.
Questions about fenwick_2d
2D Fenwick tree for point updates and rectangle sum 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.
fenwick_2d accepts 3 parameters: cols, rows, operations. Required: cols, rows, 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_2d: 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_2d 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_2d 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_2d. 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_2d 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