trigger_fmg_restore

A destructive tool on the FortiManager MCP server.

SERVERFortiManager MCP Server SOURCErstierli/fortimanager-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/rstierli-fortimanager-mcp/trigger-fmg-restore.md

WHAT IT DOES

What trigger_fmg_restore does on FortiManager MCP Server

AI agents call trigger_fmg_restore to permanently remove resources in FortiManager MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why trigger_fmg_restore is rated Critical

Restore operations typically overwrite current configuration irreversibly, suggesting destructive impact.

From the tool's definition uninformative description

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs trigger_fmg_restore safely

PolicyLayer is an MCP gateway: it sits between your AI agents and FortiManager MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For trigger_fmg_restore, this is the rule to start with:

trigger_fmg_restore Hidden

trigger_fmg_restore is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "trigger_fmg_restore"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FortiManager MCP Server, apply this rule, and every trigger_fmg_restore call is checked against it from then on.

FAQ

Questions about trigger_fmg_restore

What does the trigger_fmg_restore tool do? +

trigger_fmg_restore is a destructive tool on the FortiManager MCP Server MCP server. It is categorised as a Destructive tool in the FortiManager MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on trigger_fmg_restore? +

Register the FortiManager MCP Server MCP server in PolicyLayer and add a rule for trigger_fmg_restore: 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 MCP Server. Nothing to install.

What risk level is trigger_fmg_restore? +

trigger_fmg_restore is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit trigger_fmg_restore? +

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

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

trigger_fmg_restore is provided by the FortiManager MCP Server MCP server (rstierli/fortimanager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FortiManager MCP Server, and thousands of servers like it.

This server

All 236 FortiManager MCP Server tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →