Get fields from a Redis Hash. Retrieve specific fields or all fields.
AI agents call redis_hash_get to retrieve information from RedisNexus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query operation on Redis data structures (hash retrieval). It has no capability to modify, delete, or execute operations—it only retrieves and returns existing data. The blast radius is minimal as it cannot alter system state. Confidence is high because the verb 'Get' and 'Retrieve' unambiguously indicate read-only semantics.
From the tool's definition Tool name 'redis_hash_get' and description 'Get fields from a Redis Hash. Retrieve specific fields or all fields' indicate a read-only retrieval operation with no data modification, deletion, or side effects.
Attacks that exploit this kind of access
Get fields from a Redis Hash. Retrieve specific fields or all fields. It is categorised as a Read tool in the RedisNexus MCP Server, which means it retrieves data without modifying state.
Register the RedisNexus MCP server in PolicyLayer and add a rule for redis_hash_get: 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 RedisNexus. Nothing to install.
redis_hash_get 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 redis_hash_get 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_hash_get. 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_hash_get is provided by the RedisNexus MCP server (rajkumar-madhu/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 →