Push a value onto the left of a Redis list and optionally set an expiration time.
AI agents use lpush to create or update resources in Redis MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Redis MCP Server environment.
The lpush operation creates or modifies data in a reversible manner (the pushed value can be removed with lpop or lrem). It is not destructive since the original list data is preserved and the operation can be undone. It is not Execute-level since it doesn't run arbitrary code or trigger external operations—it's a simple data modification.
From the tool's definition Tool name is 'lpush' which performs a list push operation. Description states 'Push a value onto the left of a Redis list and optionally set an expiration time.' This modifies data by adding/inserting elements into an existing list structure.
Attacks that exploit this kind of access
Push a value onto the left of a Redis list and optionally set an expiration time. It is categorised as a Write tool in the Redis MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Redis MCP Server MCP server in PolicyLayer and add a rule for lpush: 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 Redis MCP Server. Nothing to install.
lpush 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 lpush 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 lpush. 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.
lpush is provided by the Redis MCP Server MCP server (yuchenhui/mcp-redis). 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 →