get_assertions

Get assertion summary for a given entity with its type, name, env, site, namespace, and time range

SERVERGrafana MCP Server SOURCE0xteamhq/mcp-grafana

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/0xteamhq-mcp-grafana/get-assertions.md

WHAT IT DOES

What get_assertions does on Grafana MCP Server

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

RISK

Why get_assertions is rated Low

This tool performs a read-only retrieval of assertion data. It queries existing monitoring/assertion data and returns summary information without side effects, data modification, or external operation triggers. The blast radius of misuse is minimal—an agent could retrieve assertion data it shouldn't see, but cannot alter or destroy data, execute commands, or commit financial transactions.

From the tool's definition Tool description indicates 'Get assertion summary' which retrieves data about assertions for a given entity without modifying, deleting, or executing operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_assertions safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Grafana MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_assertions, this is the rule to start with:

get_assertions Allowed

get_assertions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Grafana MCP Server, apply this rule, and every get_assertions call is checked against it from then on.

FAQ

Questions about get_assertions

What does the get_assertions tool do? +

Get assertion summary for a given entity with its type, name, env, site, namespace, and time range. It is categorised as a Read tool in the Grafana MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_assertions? +

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

What risk level is get_assertions? +

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

Can I rate-limit get_assertions? +

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

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

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

KEEP EXPLORING

More on Grafana MCP Server, and thousands of servers like it.

This server

All 43 Grafana MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →