escalate_outage

Escalate an outage to the next notification level.

SERVERUnofficial FortiMonitor MCP Server SOURCEgjenkins20/unofficial-fortimonitor-mcp-server
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/gjenkins20-unofficial-fortimonitor-mcp-server/escalate-outage.md

What escalate_outage does on Unofficial FortiMonitor MCP Server

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.

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 definition Escalate an outage to the next notification level

Questions about escalate_outage

What does the escalate_outage tool do? +

Escalate an outage to the next notification level. It is categorised as a Execute tool in the Unofficial FortiMonitor MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on escalate_outage? +

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

What risk level is escalate_outage? +

escalate_outage is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit escalate_outage? +

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

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

escalate_outage is provided by the Unofficial FortiMonitor MCP Server MCP server (gjenkins20/unofficial-fortimonitor-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Unofficial FortiMonitor MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Unofficial FortiMonitor MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.