upstash_redis_incr
Increment a numeric key in an Upstash Redis database.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/upstash-redis-incr.md
What upstash_redis_incr does on UnClick
AI agents use upstash_redis_incr 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 | Yes | |
db_id | string | Yes | |
email | string | Yes | |
api_key | string | Yes |
Parameters from the server's own tool schema.
Why upstash_redis_incr is rated Medium
Incrementing a key modifies existing data in the Redis database. This is a write operation (it changes the stored value), but it is reversible (the value can be decremented or reset), so it does not qualify as Destructive. Misuse could corrupt counters or rate-limit logic, giving it medium severity.
From the tool's definition Increment a numeric key in an Upstash Redis database
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs upstash_redis_incr 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 upstash_redis_incr, this is the rule to start with:
upstash_redis_incr 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 upstash_redis_incr call is checked against it from then on.
Questions about upstash_redis_incr
Increment a numeric key in an Upstash Redis database. 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.
upstash_redis_incr accepts 4 parameters: key, db_id, email, api_key. Required: key, db_id, email, api_key. 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 upstash_redis_incr: 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.
upstash_redis_incr 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 upstash_redis_incr 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 upstash_redis_incr. 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.
upstash_redis_incr 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