Get a list of connected clients to the Redis server.
AI agents call client_list to retrieve information from Redis MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about Redis client connections without modifying, deleting, or executing any operations. It is a read-only administrative query. The blast radius is minimal—an agent could learn about connected clients but cannot directly harm data or systems. Confidence is high due to clear evidence that this is a pure information retrieval function.
From the tool's definition Tool name 'client_list' and description 'Get a list of connected clients to the Redis server' indicate a query/retrieval operation with no side effects. Returns metadata about server connections.
Attacks that exploit this kind of access
Get a list of connected clients to the Redis server. It is categorised as a Read tool in the Redis MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Redis MCP Server MCP server in PolicyLayer and add a rule for client_list: 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.
client_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the client_list 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 client_list. 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.
client_list 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 →