Set expiration time for a key
AI agents use redis_expire to create or update resources in Mcp Database — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Database environment.
redis_expire modifies Redis data by setting or updating the expiration time on existing keys. This is a Write operation because it persistently changes data state (though reversibly). It is not Destructive because the key itself remains accessible until expiration; it is not Read because it has side effects; it is not Execute because it doesn't run arbitrary code.
From the tool's definition Tool name 'redis_expire' and description 'Set expiration time for a key' indicate modification of Redis key metadata. This is a write operation that alters key properties (TTL/expiration) but is reversible (can be set again or removed with PERSIST).
Attacks that exploit this kind of access
Set expiration time for a key. It is categorised as a Write tool in the Mcp Database MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Database MCP server in PolicyLayer and add a rule for redis_expire: 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 Mcp Database. Nothing to install.
redis_expire 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 redis_expire 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 redis_expire. 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.
redis_expire is provided by the Mcp Database MCP server (nam088/mcp-database-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →