pagerduty_list_services
List all services in a PagerDuty account. Optionally filter by name.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/pagerduty-list-services.md
What pagerduty_list_services does on UnClick
AI agents call pagerduty_list_services 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 |
|---|---|---|---|
limit | number | — | Max results |
query | string | — | Filter services by name |
api_key | string | Yes | PagerDuty API key |
Parameters from the server's own tool schema.
Why pagerduty_list_services is rated Low
This tool retrieves and queries PagerDuty service data without side effects. However, severity is elevated to medium rather than low because listing all services in a PagerDuty account could expose operational security details (service names, structure, dependencies) that might inform social engineering or targeted attacks.
From the tool's definition Tool description explicitly states 'List all services' with optional filtering by name. The verb 'list' and lack of any modification language (create, update, delete) indicate a read-only operation.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs pagerduty_list_services 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_services, this is the rule to start with:
pagerduty_list_services 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_services call is checked against it from then on.
Questions about pagerduty_list_services
List all services in a PagerDuty account. Optionally filter by name. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
pagerduty_list_services accepts 3 parameters: limit, query, api_key. 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_services: 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_services 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_services 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_services. 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_services 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