AI agents use list_push to create or update resources in MCP Server Redis — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Server Redis environment.
This tool writes new values into a Redis list, which is a reversible data modification (the pushed values can be removed later). It does not execute code, delete data, or involve financial transactions. Misuse could overwrite or flood a list with unwanted data, hence medium severity.
From the tool's definition 'Push values to a Redis list' — creates/appends data to a Redis list structure
Documented attack patterns abuse exactly the kind of access list_push gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server Redis, and nothing reaches the server without passing your rules. This is the rule we recommend for list_push:
{
"version": "1",
"default": "deny",
"tools": {
"list_push": {
"limits": [
{
"counter": "list_push_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}list_push stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Push values to a Redis list. It is categorised as a Write tool in the MCP Server Redis MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Server Redis MCP server in PolicyLayer and add a rule for 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 MCP Server Redis. Nothing to install.
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 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 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.
list_push is provided by the MCP Server Redis MCP server (prajwalnayak7/mcp-server-redis). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Server Redis, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 MCP Server Redis tools catalogued and risk-classified — across an index of 43,000+ MCP servers.