add_outage_note
Add a note or comment to an outage.
This record as markdown: /tools/gjenkins20-unofficial-fortimonitor-mcp-server/add-outage-note.md
What add_outage_note does on Unofficial FortiMonitor MCP Server
AI agents use add_outage_note 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 add_outage_note is rated Medium
This tool creates or appends data (a note/comment) to an outage record. It does not delete, overwrite, execute commands, move money, or trigger external operations. The change is reversible (notes can be deleted or edited). The blast radius is minimal—a malicious note adds clutter or misinformation to outage records but does not compromise system integrity, trigger false escalations, or cause operational harm.
From the tool's definition add_outage_note adds a note or comment to an outage, which creates new data (note/comment) associated with an existing outage record without deleting or modifying existing data irreversibly.
Attacks that exploit this kind of access
The rule that runs add_outage_note 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 add_outage_note, this is the rule to start with:
add_outage_note 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 add_outage_note call is checked against it from then on.
Questions about add_outage_note
Add a note or comment to an outage. 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 add_outage_note: 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.
add_outage_note 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 add_outage_note 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 add_outage_note. 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.
add_outage_note 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