Set a field in a hash stored at key.
AI agents use redis_hset 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.
redis_hset performs a reversible data modification operation on Redis data structures. While the change can be undone (by setting different values or deleting the field), the high severity reflects that in a multi-agent or production context, unintended writes to Redis caches could corrupt application state, invalidate cached data, or cause downstream system failures.
From the tool's definition Tool name 'redis_hset' and description 'Set a field in a hash stored at key' indicate this modifies data in Redis by setting hash field values. This is a write operation that creates or modifies data reversibly.
Attacks that exploit this kind of access
Set a field in a hash stored at key. 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_hset: 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_hset 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_hset 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_hset. 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_hset 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 →