restore_system_config
A destructive tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/restore-system-config.md
What restore_system_config does on Fortimanager
AI agents call restore_system_config to permanently remove resources in Fortimanager, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why restore_system_config is rated Critical
Restoring a system configuration overwrites the current running configuration, which is an irreversible action. Any configuration changes made after the restore point will be lost. On a FortiManager system managing network security devices, this could have a massive blast radius affecting all managed devices and policies.
From the tool's definition Tool name 'restore_system_config' — 'restore' implies overwriting current system configuration with a previous state, which is irreversible and potentially destructive to existing configuration.
Attacks that exploit this kind of access
The rule that runs restore_system_config 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 restore_system_config, this is the rule to start with:
restore_system_config is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Fortimanager, apply this rule, and every restore_system_config call is checked against it from then on.
Questions about restore_system_config
restore_system_config is a destructive tool on the Fortimanager MCP server. It is categorised as a Destructive tool in the Fortimanager MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Fortimanager MCP server in PolicyLayer and add a rule for restore_system_config: 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.
restore_system_config is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the restore_system_config 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 restore_system_config. 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.
restore_system_config 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