Low Risk

get

Get a Redis string value. Args: key (str): The key to retrieve. Returns: str, bytes: The stored value or an error message.

How to control get ↓

AI agents call get to retrieve information from Redis MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves data from Redis without modifying, deleting, or executing any operations. It is a straightforward read operation that queries existing data. The low severity reflects minimal blast radius—retrieving a value cannot cause data loss or unintended modifications, though sensitivity depends on what data is stored.

From the tool's definition Tool name is 'get' and description states 'Get a Redis string value' with argument 'key (str): The key to retrieve.' and return value 'str, bytes: The stored value or an error message.' This is a pure retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Redis MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get": {}
  }
}

get is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Redis MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get tool do? +

Get a Redis string value. Args: key (str): The key to retrieve. Returns: str, bytes: The stored value or an error message. It is categorised as a Read tool in the Redis MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get? +

Register the Redis MCP Server MCP server in PolicyLayer and add a rule for 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 Redis MCP Server. Nothing to install.

What risk level is get? +

get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get? +

Yes. Add a rate_limit block to the 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.

How do I block get completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides get? +

get is provided by the Redis MCP Server MCP server (redis/mcp-redis). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Redis MCP Server tool call.

Deterministic rules across all 53 Redis MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

53 Redis MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.