broadcast_outage

Broadcast a message about an outage to all configured notification contacts.

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

WHAT IT DOES

What broadcast_outage does on Unofficial FortiMonitor MCP Server

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

Even though broadcast_outage only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

broadcast_outage Allowed

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

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

FAQ

Questions about broadcast_outage

What does the broadcast_outage tool do? +

Broadcast a message about an outage to all configured notification contacts. 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 broadcast_outage? +

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

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

Can I rate-limit broadcast_outage? +

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

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

broadcast_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

The MCP Attack Database →

Guides

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