upstash_redis_del
Delete a key from an Upstash Redis database.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/upstash-redis-del.md
What upstash_redis_del does on UnClick
AI agents call upstash_redis_del to permanently remove resources in UnClick, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| 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_del is rated Critical
The tool performs an irreversible delete operation on a database key. This is a destructive action that cannot be undone. While the blast radius is limited to a single key rather than an entire database, unauthorized deletion of data in a production Redis instance could cause application failures, data loss, and service disruption.
From the tool's definition Tool name 'upstash_redis_del' and description 'Delete a key from an Upstash Redis database' explicitly indicate irreversible deletion of data.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs upstash_redis_del 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_del, this is the rule to start with:
upstash_redis_del is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every upstash_redis_del call is checked against it from then on.
Questions about upstash_redis_del
Delete a key from an Upstash Redis database. It is categorised as a Destructive tool in the UnClick MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
upstash_redis_del 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_del: 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_del is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the upstash_redis_del 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_del. 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_del 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