list_oncall_schedules

List Grafana OnCall schedules, optionally filtering by team ID

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/list-oncall-schedules.md

What list_oncall_schedules does on Grafana MCP Server

AI agents call list_oncall_schedules 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.

Why list_oncall_schedules is rated Low

This tool queries and returns oncall schedule data without side effects. It is purely informational, supporting schedule visibility for monitoring and incident response workflows. The optional team ID filter is a read parameter that does not alter state. Classification as Read is appropriate with low severity since exposure of schedule information poses minimal risk compared to execution or financial operations.

From the tool's definition Tool name 'list_oncall_schedules' and description 'List Grafana OnCall schedules' indicate a retrieval operation with optional filtering. No modification, execution, or destructive operations are performed.

Questions about list_oncall_schedules

What does the list_oncall_schedules tool do? +

List Grafana OnCall schedules, optionally filtering by team ID. 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 list_oncall_schedules? +

Register the Grafana MCP Server 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 Grafana MCP Server. Nothing to install.

What risk level is list_oncall_schedules? +

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

Can I rate-limit list_oncall_schedules? +

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.

How do I block list_oncall_schedules completely? +

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.

What MCP server provides list_oncall_schedules? +

list_oncall_schedules 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.

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Grafana MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.