pagerduty_list_on_calls

A read tool on the Integrations MCP server.

SERVERIntegrations MCP SOURCEshriram-vasudevan/integrations-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/shriram-vasudevan-integrations-mcp/pagerduty-list-on-calls.md

WHAT IT DOES

What pagerduty_list_on_calls does on Integrations MCP

AI agents call pagerduty_list_on_calls to retrieve information from Integrations MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why pagerduty_list_on_calls is rated Low

This tool retrieves current on-call status information from PagerDuty with no side effects—it queries and returns data. No modifications, deletions, or external state changes occur. While the description is empty, the naming convention and context from similar tools strongly indicates a read-only operation. Confidence is slightly reduced due to missing description, but the tool name is sufficiently explicit.

From the tool's definition Tool name 'pagerduty_list_on_calls' indicates a query/retrieval operation for listing on-call personnel. The 'list' verb and 'get' pattern in sibling tools (airtable_list_bases, airtable_list_records, amplitude_get_active_users) consistently map to Read…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pagerduty_list_on_calls safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pagerduty_list_on_calls, this is the rule to start with:

pagerduty_list_on_calls Allowed

pagerduty_list_on_calls is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pagerduty_list_on_calls": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every pagerduty_list_on_calls call is checked against it from then on.

FAQ

Questions about pagerduty_list_on_calls

What does the pagerduty_list_on_calls tool do? +

pagerduty_list_on_calls is a read tool on the Integrations MCP server. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pagerduty_list_on_calls? +

Register the Integrations MCP server in PolicyLayer and add a rule for pagerduty_list_on_calls: 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 Integrations MCP. Nothing to install.

What risk level is pagerduty_list_on_calls? +

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

Can I rate-limit pagerduty_list_on_calls? +

Yes. Add a rate_limit block to the pagerduty_list_on_calls 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 pagerduty_list_on_calls completely? +

Set action: deny in the PolicyLayer policy for pagerduty_list_on_calls. 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 pagerduty_list_on_calls? +

pagerduty_list_on_calls is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Integrations, and thousands of servers like it.

This server

All 420 Integrations tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →