Query logs for a service within a time range. Auto-detects the log datasource and service label by scanning Loki labels — previously resolved services are cached so repeat calls skip detection. Output mode is user-selectable:
AI agents call query_logs to retrieve information from Grafana without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
query_logs retrieves log data without modifying, deleting, or executing external operations. It is a read operation with caching for efficiency. The server explicitly advertises 'read-only access', and the tool performs queries and data retrieval—classic Read category behavior. Severity is low because querying logs poses minimal risk; the worst case is information disclosure of logs already accessible to the user.
From the tool's definition Tool description states 'Query logs for a service within a time range' and 'read-only access to log data' per server description. No mutations, deletions, or external operations triggered.
Attacks that exploit this kind of access
Query logs for a service within a time range. Auto-detects the log datasource and service label by scanning Loki labels — previously resolved services are cached so repeat calls skip detection. Output mode is user-selectable:. It is categorised as a Read tool in the Grafana MCP Server, which means it retrieves data without modifying state.
Register the Grafana MCP server in PolicyLayer and add a rule for query_logs: 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. Nothing to install.
query_logs 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 query_logs 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 query_logs. 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.
query_logs is provided by the Grafana MCP server (ninanung/grafana-mcp). 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 →