export_outage_history

Export active outage history in CSV format.

SERVERUnofficial FortiMonitor MCP Server SOURCEgjenkins20/unofficial-fortimonitor-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What export_outage_history does on Unofficial FortiMonitor MCP Server

AI agents call export_outage_history to retrieve information from Unofficial FortiMonitor MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why export_outage_history is rated Low

This tool retrieves and exports historical outage data in CSV format. It is a read-only operation with no side effects — it queries existing outage records and returns them. No data is created, modified, or deleted.

From the tool's definition Export active outage history in CSV format

Attacks that exploit this kind of access

RECOMMENDED RULE

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

export_outage_history Allowed

export_outage_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "export_outage_history": {}
  }
}

ALLOW ONLY 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 export_outage_history call is checked against it from then on.

FAQ

Questions about export_outage_history

What does the export_outage_history tool do? +

Export active outage history in CSV format. It is categorised as a Read tool in the Unofficial FortiMonitor MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on export_outage_history? +

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

export_outage_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit export_outage_history? +

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

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

export_outage_history 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

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →