Get assertion summary for a given entity with its type, name, env, site, namespace, and time range
AI agents call get_assertions to retrieve information from Mcp Grafana without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries assertion summary data without creating, modifying, executing code, or deleting anything. It is a straightforward read operation that fetches monitoring/observability data from Grafana, consistent with other Read category tools on this server like 'get_alert_rule_by_uid' and 'get_dashboard_by_uid'. Misuse would only expose information, not cause operational damage.
From the tool's definition Tool name is 'get_assertions' and description states 'Get assertion summary' - uses get/retrieve pattern indicating data retrieval with no modification capabilities.
Attacks that exploit this kind of access
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 Mcp Grafana MCP Server, which means it retrieves data without modifying state.
Register the Mcp Grafana 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 Mcp Grafana. Nothing to install.
get_assertions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
get_assertions is provided by the Mcp Grafana MCP server (@leval/mcp-grafana). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →