Low Risk

get_datastore

Get information about a specific data store.

How to control get_datastore ↓

What get_datastore does on Prometheus MCP Server

AI agents call get_datastore 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 get_datastore needs a policy

This tool retrieves or queries information about a data store without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal blast radius if misused by an AI agent—the worst outcome would be unauthorized information disclosure about a data store's configuration or metadata.

From the tool's definition Tool name 'get_datastore' and description 'Get information about a specific data store' indicate a retrieval operation with no modification or execution of code.

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

How to control get_datastore

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 get_datastore:

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

get_datastore 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 get_datastore

What does the get_datastore tool do? +

Get information about a specific data store. 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 get_datastore? +

Register the Prometheus MCP Server MCP server in PolicyLayer and add a rule for get_datastore: 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 get_datastore? +

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

Can I rate-limit get_datastore? +

Yes. Add a rate_limit block to the get_datastore 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_datastore completely? +

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

get_datastore 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.