unclick_kv_set
Store a value in the UnClick key-value store with optional TTL.
This record as markdown: /tools/creativelead-unclick/unclick-kv-set.md
What unclick_kv_set does on UnClick
AI agents use unclick_kv_set 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 |
|---|---|---|---|
key | string | — | |
ttl | number | — | Seconds until expiry (optional) |
value | object | — | Any JSON-serializable value |
Parameters from the server's own tool schema.
Why unclick_kv_set is rated Medium
This tool creates or modifies data in a key-value store. It is reversible—stored values can be overwritten or expire via TTL—making it Write rather than Destructive. The severity is medium because misuse could pollute the shared key-value store, affect other agents or processes relying on this data, or cause application failures through incorrect state, but the impact is limited to this service's internal storage…
From the tool's definition The tool description states it will 'Store a value in the UnClick key-value store', which is a data modification operation. The inclusion of 'optional TTL' indicates the stored data is reversible (will expire or can be overwritten).
Attacks that exploit this kind of access
The rule that runs unclick_kv_set 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 unclick_kv_set, this is the rule to start with:
unclick_kv_set 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 unclick_kv_set call is checked against it from then on.
Questions about unclick_kv_set
Store a value in the UnClick key-value store with optional TTL. 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.
unclick_kv_set accepts 3 parameters: key, ttl, value. 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 unclick_kv_set: 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.
unclick_kv_set 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 unclick_kv_set 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 unclick_kv_set. 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.
unclick_kv_set is provided by the UnClick MCP server (creativelead/unclick). 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