upstash_redis_del

Delete a key from an Upstash Redis database.

Server UnClick @unclick/mcp-server
Category Destructive
Risk class Critical
Parameters 44 required

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.

ParameterTypeRequiredDescription
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 needs a policy

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)

Questions about upstash_redis_del

What does the upstash_redis_del tool do? +

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.

What parameters does upstash_redis_del accept? +

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.

How do I enforce a policy on upstash_redis_del? +

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.

What risk level is upstash_redis_del? +

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.

Can I rate-limit upstash_redis_del? +

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.

How do I block upstash_redis_del completely? +

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.

What MCP server provides upstash_redis_del? +

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.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.