hash_get

THE RISK

Low Risk

Why hash_get needs a policy

This tool retrieves data from a Redis hash structure without modifying, deleting, or executing arbitrary code. It is a straightforward read operation consistent with other query tools like 'get_value' and 'list_range' on this server.

From the tool's definition Tool name 'hash_get' and description 'Get hash fields' indicate a retrieval operation with no side effects. Redis HGET/HGETALL commands are read-only queries.

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

POLICY

How to control hash_get

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hash_get": {}
  }
}

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

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP Server Redis tools

Destructive delete_key Delete a Redis key Execute publish_message Publish a message to a Redis channel Write list_push Push values to a Redis list Write hash_set Set multiple hash fields Write set_add Add members to a Redis set Write set_value Set value for a Redis key Read get_value Get value for a Redis key Read list_range Get a range of values from a Redis list

All 10 MCP Server Redis tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about hash_get

What does the hash_get tool do? +

Get hash fields. It is categorised as a Read tool in the MCP Server Redis MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on hash_get? +

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

What risk level is hash_get? +

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

Can I rate-limit hash_get? +

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

How do I block hash_get completely? +

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

What MCP server provides hash_get? +

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

Enforce policy on every MCP Server Redis tool call.

Start from MCP Server Redis, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →