AI agents call set_members to retrieve information from Redis MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves all members from a Redis set, which is a pure read operation equivalent to the Redis SMEMBERS command. No data is modified, created, or deleted.
From the tool's definition 获取集合所有成员 means 'Get all members of a set' — a read/retrieval operation with no side effects
Attacks that exploit this kind of access
获取集合所有成员. It is categorised as a Read tool in the Redis MCP MCP Server, which means it retrieves data without modifying state.
Register the Redis MCP server in PolicyLayer and add a rule for set_members: 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. Nothing to install.
set_members 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 set_members 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 set_members. 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.
set_members is provided by the Redis MCP server (pickstar-2002/redis-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 →