create_historical_outage

Create a historical outage record. Use this to manually add past incidents

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/create-historical-outage.md

WHAT IT DOES

What create_historical_outage does on Unofficial FortiMonitor MCP Server

AI agents use create_historical_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.

RISK

Why create_historical_outage is rated Medium

This tool creates new historical outage records, which modifies the monitoring database. While it operates on past data and is reversible (records can be deleted), it affects the integrity of historical incident logs that may be used for auditing, SLA calculations, and reporting.

From the tool's definition Tool name includes 'create' and description states 'manually add past incidents', indicating data creation/modification of outage records.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_historical_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 create_historical_outage, this is the rule to start with:

create_historical_outage Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_historical_outage": {
      "limits": [
        {
          "counter": "create_historical_outage_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Unofficial FortiMonitor MCP Server, apply this rule, and every create_historical_outage call is checked against it from then on.

FAQ

Questions about create_historical_outage

What does the create_historical_outage tool do? +

Create a historical outage record. Use this to manually add past incidents. 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 create_historical_outage? +

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

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

Can I rate-limit create_historical_outage? +

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

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

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

KEEP EXPLORING

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

This server

All 272 Unofficial FortiMonitor MCP Server tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →