list_resolved_outages

List resolved (no longer active) outages.

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/list-resolved-outages.md

WHAT IT DOES

What list_resolved_outages does on Unofficial FortiMonitor MCP Server

AI agents call list_resolved_outages 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 list_resolved_outages is rated Low

This tool queries and returns historical outage data that is already resolved. It performs no modifications, deletions, or external operations. The action is purely informational—retrieving past events for monitoring and analysis purposes. Listing historical data poses minimal risk even if misused by an agent, as it only exposes already-concluded events.

From the tool's definition Tool name 'list_resolved_outages' and description 'List resolved (no longer active) outages' indicate a data retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_resolved_outages Allowed

list_resolved_outages 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": {
    "list_resolved_outages": {}
  }
}

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

FAQ

Questions about list_resolved_outages

What does the list_resolved_outages tool do? +

List resolved (no longer active) outages. 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 list_resolved_outages? +

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

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

Can I rate-limit list_resolved_outages? +

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

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

list_resolved_outages 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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