pagerduty_list_oncalls
List who is currently on-call in PagerDuty, optionally filtered by schedule or user.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/pagerduty-list-oncalls.md
What pagerduty_list_oncalls does on UnClick
AI agents call pagerduty_list_oncalls to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | Yes | PagerDuty API key |
user_ids | string | — | Filter by user ID |
schedule_ids | string | — | Filter by schedule ID |
Parameters from the server's own tool schema.
Why pagerduty_list_oncalls is rated Low
This tool retrieves on-call schedule information from PagerDuty. It is a read operation with no side effects—it only queries and returns data. However, severity is medium rather than low because on-call roster information can be sensitive operational data; an AI agent listing this information could leak details about personnel availability, schedules, and incident response readiness to unauthorized parties,…
From the tool's definition Tool name 'list_oncalls' and description 'List who is currently on-call' indicate a retrieval operation that queries PagerDuty for on-call personnel data without modifying it.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs pagerduty_list_oncalls safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pagerduty_list_oncalls, this is the rule to start with:
pagerduty_list_oncalls is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every pagerduty_list_oncalls call is checked against it from then on.
Questions about pagerduty_list_oncalls
List who is currently on-call in PagerDuty, optionally filtered by schedule or user. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
pagerduty_list_oncalls accepts 3 parameters: api_key, user_ids, schedule_ids. Required: api_key. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for pagerduty_list_oncalls: 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 UnClick. Nothing to install.
pagerduty_list_oncalls 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 pagerduty_list_oncalls 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 pagerduty_list_oncalls. 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.
pagerduty_list_oncalls is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue