Low Risk

hash_get

Get field from hash.

How to control hash_get ↓

What hash_get does on Prometheus MCP Server

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

Low Risk

Why hash_get needs a policy

This tool retrieves a value from a hash data structure. The 'Get' verb and absence of any language suggesting mutation, deletion, or external effects indicates a Read operation. Even if hash_get were operating on external state, retrieval alone presents minimal risk. Severity is low because reading individual hash fields has a limited blast radius and no irreversible consequences.

From the tool's definition Tool name 'hash_get' and description 'Get field from hash' indicate a retrieval operation with no modification or side effects.

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

How to control hash_get

PolicyLayer is an MCP gateway — it sits between your AI agents and Prometheus MCP Server, 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.

  1. Create a free account and register Prometheus 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.

Related tools and policies

Go deeper

Questions about hash_get

What does the hash_get tool do? +

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

How do I enforce a policy on hash_get? +

Register the Prometheus MCP Server 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 Prometheus MCP Server. 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 Prometheus MCP Server MCP server (awslabs.prometheus-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Prometheus MCP Server tool call.

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

Free to start. No card required.

805 Prometheus MCP Server tools catalogued and risk-classified — across an index of 43,000+ 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.