# escalate_outage

Escalate an outage to the next notification level.

Agent View of the PolicyLayer registry record for `escalate_outage`. HTML page: https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/escalate-outage

## Facts

- Tool: `escalate_outage`
- Server: Unofficial FortiMonitor MCP Server (`gjenkins20/unofficial-fortimonitor-mcp-server`) — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server.md
- Homepage: https://github.com/gjenkins20/unofficial-fortimonitor-mcp-server
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "escalate_outage",
    "arguments": {}
  }
}
```

## Why escalate_outage is rated High

Escalating an outage triggers external operations — sending notifications to the next escalation tier, potentially alerting additional personnel or systems. This is an action with real-world side effects (notifications, on-call paging, etc.) that goes beyond simply writing data, making Execute the most appropriate category. Misuse could cause unnecessary alerting, staff disruption, or mask true incident status.

From the tool's own definition: "Escalate an outage to the next notification level"

## Use case

AI agents invoke escalate_outage to trigger actions in Unofficial FortiMonitor MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Unofficial FortiMonitor MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "escalate_outage": {
      "limits": [
        {
          "counter": "escalate_outage_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Unofficial FortiMonitor MCP Server (271)

- `clear_webhook_events` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/clear-webhook-events.md
- `delete_agent_resource_threshold` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-agent-resource-threshold.md
- `delete_cloud_credential` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-cloud-credential.md
- `delete_compound_service` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-compound-service.md
- `delete_contact` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-contact.md
- `delete_contact_group` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-contact-group.md
- `delete_contact_info` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-contact-info.md
- `delete_dashboard` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-dashboard.md
- `delete_dem_application` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-dem-application.md
- `delete_fabric_connection` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-fabric-connection.md
- `delete_maintenance_schedule` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-maintenance-schedule.md
- `delete_network_service` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-network-service.md
- `delete_network_service_countermeasure` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-network-service-countermeasure.md
- `delete_notification_schedule` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-notification-schedule.md
- `delete_onsight` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-onsight.md
- `delete_onsight_group` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-onsight-group.md
- `delete_rotating_contact` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-rotating-contact.md
- `delete_server` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-server.md
- `delete_server_attribute` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-server-attribute.md
- `delete_server_attribute_type` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-server-attribute-type.md
- `delete_server_group` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-server-group.md
- `delete_server_path_monitoring` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-server-path-monitoring.md
- `delete_server_template` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-server-template.md
- `delete_snmp_credential` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-snmp-credential.md
- `delete_snmp_resource` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-snmp-resource.md
- `delete_status_page` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-status-page.md
- `delete_threshold_countermeasure` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-threshold-countermeasure.md
- `delete_user` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/delete-user.md
- `force_resolve_outage` — Destructive — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/force-resolve-outage.md
- `flush_server_dns` — Execute — https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server/flush-server-dns.md
- …and 241 more: https://policylayer.com/tools/gjenkins20-unofficial-fortimonitor-mcp-server.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=gjenkins20-unofficial-fortimonitor-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/gjenkins20-unofficial-fortimonitor-mcp-server