persistent_array
Persistent array with version-controlled get/set operations using a persistent segment tree.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/persistent-array.md
What persistent_array does on UnClick
AI agents use persistent_array to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
initial | array | Yes | Initial array values |
operations | array | Yes | Operations: {type:'get'|'set', version, index, value?} |
Parameters from the server's own tool schema.
Why persistent_array is rated Medium
This tool supports both retrieval (get) and modification (set) of data in a persistent structure. Since it includes write capability that modifies stored state, it falls under Write rather than Read. Severity is medium because misuse could corrupt or overwrite data in the array, but the blast radius is limited to the array itself rather than system-wide or financial impact.
From the tool's definition Tool description specifies 'get/set operations', indicating both read and write capabilities. The 'set operations' combined with 'persistent' storage means data is created or modified and persisted.
Attacks that exploit this kind of access
The rule that runs persistent_array 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 persistent_array, this is the rule to start with:
persistent_array stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 persistent_array call is checked against it from then on.
Questions about persistent_array
Persistent array with version-controlled get/set operations using a persistent segment tree. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
persistent_array accepts 2 parameters: initial, operations. Required: initial, 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 persistent_array: 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.
persistent_array is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the persistent_array 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 persistent_array. 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.
persistent_array 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.
This server
Across the catalogue