Push values to a Redis List. Use 'left' for LPUSH (stack/queue head)
AI agents use redis_list_push to create or update resources in RedisNexus — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RedisNexus environment.
This tool writes new data to a Redis list by pushing values onto it. It creates or modifies data in Redis (reversibly, as values can be removed), making it a Write operation. Misuse could lead to memory exhaustion or data corruption in production Redis instances, warranting medium severity.
From the tool's definition Push values to a Redis List. Use 'left' for LPUSH (stack/queue head)
Attacks that exploit this kind of access
Push values to a Redis List. Use 'left' for LPUSH (stack/queue head). It is categorised as a Write tool in the RedisNexus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RedisNexus MCP server in PolicyLayer and add a rule for redis_list_push: 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 RedisNexus. Nothing to install.
redis_list_push 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_list_push 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_list_push. 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_list_push is provided by the RedisNexus MCP server (rajkumar-madhu/mcp). 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 →