MCP Tool Reference Low Risk

query_elasticsearch

Search using Lucene or Query DSL

Part of the Grafana MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

WHEN AI AGENTS USE THIS TOOL

AI agents call query_elasticsearch to retrieve information from Grafana without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions — but you may still want rate limits to control API costs.

WHY ENFORCE A POLICY ON QUERY_ELASTICSEARCH

Even though query_elasticsearch only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

grafana.yaml
tools:
  query_elasticsearch:
    rules:
      - action: allow

See the full Grafana policy for all 29 tools.

DETAILS

Tool Name

query_elasticsearch

Category

Read

MCP Server

Grafana MCP Server

Risk Level

Low

MORE GRAFANA TOOLS

View all 29 tools →

SIMILAR READ TOOLS ON OTHER SERVERS

RELATED READING

FREQUENTLY ASKED QUESTIONS

What does the query_elasticsearch tool do?

Search using Lucene or Query DSL. It is categorised as a Read tool in the Grafana MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_elasticsearch?

Add a rule in your Intercept YAML policy under the tools section for query_elasticsearch. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Grafana MCP server.

What risk level is query_elasticsearch?

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

Can I rate-limit query_elasticsearch?

Yes. Add a rate_limit block to the query_elasticsearch rule in your Intercept 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 query_elasticsearch completely?

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

query_elasticsearch is provided by the Grafana MCP server (grafana/mcp-grafana). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

ENFORCE POLICIES ON GRAFANA

Open source. One binary. Zero dependencies.