MCP Tool Reference Critical Risk

delete_alert_grouping_setting

Delete an alert grouping setting

Part of the PagerDuty MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

pagerduty-mcp Destructive

WHEN AI AGENTS USE THIS TOOL

AI agents may call delete_alert_grouping_setting to permanently remove or destroy resources in PagerDuty. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

WHY ENFORCE A POLICY ON DELETE_ALERT_GROUPING_SETTING

Without a policy, an AI agent could call delete_alert_grouping_setting in a loop, permanently destroying resources in PagerDuty. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

RECOMMENDED POLICY

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

pagerduty.yaml
tools:
  delete_alert_grouping_setting:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full PagerDuty policy for all 62 tools.

DETAILS

Tool Name

delete_alert_grouping_setting

Category

Destructive

Risk Level

Critical

MORE PAGERDUTY TOOLS

View all 62 tools →

SIMILAR DESTRUCTIVE TOOLS ON OTHER SERVERS

RELATED READING

FREQUENTLY ASKED QUESTIONS

What does the delete_alert_grouping_setting tool do?

Delete an alert grouping setting. It is categorised as a Destructive tool in the PagerDuty MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_alert_grouping_setting?

Add a rule in your Intercept YAML policy under the tools section for delete_alert_grouping_setting. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the PagerDuty MCP server.

What risk level is delete_alert_grouping_setting?

delete_alert_grouping_setting is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_alert_grouping_setting?

Yes. Add a rate_limit block to the delete_alert_grouping_setting rule in your Intercept 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 delete_alert_grouping_setting completely?

Set action: deny in the Intercept policy for delete_alert_grouping_setting. 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 delete_alert_grouping_setting?

delete_alert_grouping_setting is provided by the PagerDuty MCP server (pagerduty-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

ENFORCE POLICIES ON PAGERDUTY

Open source. One binary. Zero dependencies.