delay_outage

Delay outage notifications by a specified number of minutes.

SERVERUnofficial FortiMonitor MCP Server SOURCEgjenkins20/unofficial-fortimonitor-mcp-server
Medium RISK CLASS
Category Write
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/delay-outage.md

What delay_outage does on Unofficial FortiMonitor MCP Server

AI agents use delay_outage to create or update resources in Unofficial FortiMonitor MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unofficial FortiMonitor MCP Server environment.

Why delay_outage is rated Medium

This tool modifies the timing/state of outage notifications by deferring them. It is a reversible modification to notification scheduling state (the outage still exists, only its notification timing is adjusted). It does not delete data, execute code, or involve financial transactions. Severity is medium because misuse could suppress timely alerting for real outages, potentially delaying incident response.

From the tool's definition Delay outage notifications by a specified number of minutes

Questions about delay_outage

What does the delay_outage tool do? +

Delay outage notifications by a specified number of minutes. It is categorised as a Write tool in the Unofficial FortiMonitor MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on delay_outage? +

Register the Unofficial FortiMonitor MCP Server MCP server in PolicyLayer and add a rule for delay_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 delay_outage? +

delay_outage is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit delay_outage? +

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

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

delay_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.

Across the catalogue

// 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.