delay_outage
Delay outage notifications by a specified number of minutes.
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
Attacks that exploit this kind of access
The rule that runs delay_outage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unofficial FortiMonitor MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delay_outage, this is the rule to start with:
delay_outage stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Unofficial FortiMonitor MCP Server, apply this rule, and every delay_outage call is checked against it from then on.
Questions about delay_outage
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.
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.
delay_outage is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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