rollback_device_install

THE RISK

Critical Risk

Why rollback_device_install needs a policy

Rolling back a device to a previous installation state overwrites the current configuration irreversibly. The current running state is lost and cannot be recovered without another deliberate action. This affects potentially critical network infrastructure (FortiManager manages firewalls/network devices), giving it a high blast radius if misused.

From the tool's definition rollback_device_install: 'Rollback a device to previous installation state'

Documented attack patterns abuse exactly the kind of access rollback_device_install gives an agent:

POLICY

How to control rollback_device_install

PolicyLayer is an MCP gateway — it sits between your AI agents and Fortimanager, and nothing reaches the server without passing your rules. This is the rule we recommend for rollback_device_install:

policy.json

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

rollback_device_install disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Fortimanager — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Fortimanager tools

Destructive bulk_delete_security_profile_entries bulk_delete_security_profile_entries Destructive clear_database_cache clear_database_cache Destructive delete_adom_revision delete_adom_revision Destructive delete_central_dnat_policy Delete a central DNAT policy. Destructive delete_central_snat_policy Delete a central SNAT policy. Destructive delete_certificate_template delete_certificate_template Destructive delete_cli_script delete_cli_script Destructive delete_cli_template Delete a CLI template.

All 584 Fortimanager tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Fortimanager → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about rollback_device_install

What does the rollback_device_install tool do? +

Rollback a device to previous installation state. 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.

How do I enforce a policy on rollback_device_install? +

Register the Fortimanager MCP server in PolicyLayer and add a rule for rollback_device_install: 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.

What risk level is rollback_device_install? +

rollback_device_install 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 rollback_device_install? +

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

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

rollback_device_install 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.

Enforce policy on every Fortimanager tool call.

Start from Fortimanager, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →