upgrade_adom
A execute tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/upgrade-adom.md
What upgrade_adom does on Fortimanager
AI agents invoke upgrade_adom to trigger actions in Fortimanager. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why upgrade_adom is rated High
An ADOM upgrade in FortiManager typically involves applying firmware or configuration upgrades to an administrative domain, which is an Execute-level operation with potentially broad impact. However, the empty description lowers confidence. Given the context of FortiManager and sibling tools (policy installs, device management), this likely triggers a significant system-level operation.
From the tool's definition Tool name 'upgrade_adom' suggests upgrading an ADOM (Administrative Domain) in FortiManager; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs upgrade_adom safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fortimanager, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For upgrade_adom, this is the rule to start with:
upgrade_adom stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Fortimanager, apply this rule, and every upgrade_adom call is checked against it from then on.
Questions about upgrade_adom
upgrade_adom is a execute tool on the Fortimanager MCP server. It is categorised as a Execute tool in the Fortimanager MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Fortimanager MCP server in PolicyLayer and add a rule for upgrade_adom: 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 Fortimanager. Nothing to install.
upgrade_adom is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the upgrade_adom 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 upgrade_adom. 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.
upgrade_adom is provided by the Fortimanager MCP server (jmpijll/fortimanager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Fortimanager, and thousands of servers like it.
Across the catalogue