Get common time range presets for Grafana
AI agents call get_time_range_presets to retrieve information from Grafana MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves preset time range configurations (e.g., 'last 24 hours', 'last 7 days') from Grafana. It is a simple data query operation with no side effects, no code execution, no data modification, and no destructive capabilities. The blast radius of misuse is minimal—an agent could only retrieve metadata about available time ranges.
From the tool's definition Tool name 'get_time_range_presets' and description 'Get common time range presets for Grafana' indicate a retrieval operation that returns configuration data without modifying state or triggering external operations.
Attacks that exploit this kind of access
Get common time range presets for Grafana. It is categorised as a Read tool in the Grafana MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Grafana MCP Server MCP server in PolicyLayer and add a rule for get_time_range_presets: 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.
get_time_range_presets 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_time_range_presets 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_time_range_presets. 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_time_range_presets is provided by the Grafana MCP Server MCP server (quanticsoul4772/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 →