List Grafana OnCall schedules, optionally filtering by team ID
AI agents call list_oncall_schedules 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 lists existing OnCall schedule data, which is a read-only operation. It accepts optional filter parameters but does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal—an attacker could only view schedule information they may not be authorized to see, not disrupt systems or cause irreversible damage.
From the tool's definition Tool name 'list_oncall_schedules' and description 'List Grafana OnCall schedules, optionally filtering by team ID' indicate a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List Grafana OnCall schedules, optionally filtering by team ID. 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 list_oncall_schedules: 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.
list_oncall_schedules 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 list_oncall_schedules 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 list_oncall_schedules. 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.
list_oncall_schedules 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 →