设置哈希字段。
AI agents use redis_hset to create or update resources in Redis CRUD MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Redis CRUD MCP Server environment.
redis_hset modifies data in Redis by setting a field within a hash data structure. This is a reversible write operation—the field can be updated or deleted later. It does not delete data irreversibly (thus not Destructive), does not execute arbitrary code (thus not Execute), involves no financial transactions, and has deterministic effects based on the key and field arguments.
From the tool's definition Tool name 'redis_hset' combined with server description stating 'full CRUD functionality' and the presence of sibling tools like 'redis_set', 'redis_del' indicates write operations.
Attacks that exploit this kind of access
设置哈希字段。. It is categorised as a Write tool in the Redis CRUD MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Redis CRUD 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 Redis CRUD 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 Redis CRUD MCP Server MCP server (nicolas-one/redis-crud-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 →