Get a value from Redis by key. Automatically detects the data type and returns
AI agents call redis_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 retrieves data from Redis by key lookup. It performs a query operation with no side effects—it does not create, modify, delete, or execute arbitrary code. The automatic data type detection is a convenience feature that does not change the read-only nature of the operation. Even in a production environment, read access to cached data presents minimal risk compared to write or destructive operations.
From the tool's definition Tool name and description: 'Get a value from Redis by key'. The verb 'Get' and action of retrieval with no mention of modification, deletion, or side effects clearly indicate a read operation.
Attacks that exploit this kind of access
Get a value from Redis by key. Automatically detects the data type and returns. 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_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_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_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_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_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 →