Set value in a hash field
AI agents use redis_hset to create or update resources in Mcp Database — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Database environment.
HSET modifies data in Redis by setting hash field values. This is a Write operation (reversible data modification) rather than Read (no side effects), Execute (arbitrary code), Destructive (irreversible), or Financial. Severity is medium because unintended hash modifications could corrupt application state, but the operation is reversible via subsequent HSET calls.
From the tool's definition Tool name 'redis_hset' and description 'Set value in a hash field' indicate a data modification operation. HSET is a Redis command that creates or updates hash field values, which is a reversible write operation.
Attacks that exploit this kind of access
Set value in a hash field. It is categorised as a Write tool in the Mcp Database MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Database 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 Mcp Database. 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 Mcp Database MCP server (nam088/mcp-database-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 →