Set a key-value pair in Redis.
AI agents use redis_set to create or update resources in Redshift MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Redshift MCP Server environment.
The redis_set tool modifies data by setting key-value pairs in Redis. This is a Write category action because it creates or updates data reversibly—values can be overwritten or deleted later. Severity is medium because misuse could corrupt application state or cache, but the impact is typically limited to the Redis instance and reversible. Confidence is high based on clear semantics of the 'set' operation in Redis.
From the tool's definition Tool name 'redis_set' and description 'Set a key-value pair in Redis' indicates the tool creates or modifies data in a Redis store. This is a reversible write operation.
Attacks that exploit this kind of access
Set a key-value pair in Redis. It is categorised as a Write tool in the Redshift MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Redshift MCP Server MCP server in PolicyLayer and add a rule for redis_set: 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 Redshift MCP Server. Nothing to install.
redis_set 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_set 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_set. 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_set is provided by the Redshift MCP Server MCP server (santosh07401/redshift-mcp-server). 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 →