set_outage_lead
Set the lead person on an outage.
This record as markdown: /tools/gjenkins20-unofficial-fortimonitor-mcp-server/set-outage-lead.md
What set_outage_lead does on Unofficial FortiMonitor MCP Server
AI agents use set_outage_lead 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 set_outage_lead is rated Medium
This tool modifies outage metadata by setting a responsible person, which is a reversible write operation. It does not execute code, delete data, or move money. Severity is medium because incorrect assignment of outage leads could delay incident response or create confusion in a monitoring system, but the effect is reversible and limited to administrative metadata.
From the tool's definition Tool name 'set_outage_lead' and description 'Set the lead person on an outage' indicate a modification operation that assigns/updates an attribute (the lead person) on an outage record.
Attacks that exploit this kind of access
The rule that runs set_outage_lead 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 set_outage_lead, this is the rule to start with:
set_outage_lead 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 set_outage_lead call is checked against it from then on.
Questions about set_outage_lead
Set the lead person on 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 set_outage_lead: 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.
set_outage_lead 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 set_outage_lead 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 set_outage_lead. 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.
set_outage_lead 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