Low Risk

backup_system_config

backup_system_config

How to control backup_system_config ↓

What backup_system_config does on Fortimanager

AI agents call backup_system_config as a supporting operation in Fortimanager workflows.

Low Risk

Why backup_system_config needs a policy

The name suggests creating a backup of system configuration, which could be a Read (exporting/copying data) or Write (storing a backup artifact) operation. Without a description, it's unclear whether this triggers a backup download, writes to a remote location, or has other side effects. Lowering confidence due to empty description.

From the tool's definition Tool name is 'backup_system_config'; description is empty and uninformative.

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

How to control backup_system_config

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 backup_system_config:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "backup_system_config": {
      "limits": [
        {
          "counter": "backup_system_config_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

backup_system_config gets a rate cap, and everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Fortimanager — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
SET A RULE FOR THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about backup_system_config

What does the backup_system_config tool do? +

backup_system_config. It is categorised as a Other tool in the Fortimanager MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on backup_system_config? +

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

What risk level is backup_system_config? +

backup_system_config is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit backup_system_config? +

Yes. Add a rate_limit block to the backup_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.

How do I block backup_system_config completely? +

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

What MCP server provides backup_system_config? +

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

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.

Free to start. No card required.

584 Fortimanager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.