export_adom_config

Export ADOM configuration for backup purposes.

SERVERFortimanager SOURCEjmpijll/fortimanager-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/jmpijll-fortimanager-mcp/export-adom-config.md

WHAT IT DOES

What export_adom_config does on Fortimanager

AI agents call export_adom_config to retrieve information from Fortimanager without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why export_adom_config is rated Low

The tool exports/reads configuration data for backup, which is a read-only operation with no side effects. It retrieves existing configuration without modifying, deleting, or executing anything. Severity is low as it only reads configuration data, though the exported data could contain sensitive network configuration information.

From the tool's definition Export ADOM configuration for backup purposes

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs export_adom_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 export_adom_config, this is the rule to start with:

export_adom_config Allowed

export_adom_config is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "export_adom_config": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about export_adom_config

What does the export_adom_config tool do? +

Export ADOM configuration for backup purposes. It is categorised as a Read tool in the Fortimanager MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on export_adom_config? +

Register the Fortimanager MCP server in PolicyLayer and add a rule for export_adom_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 export_adom_config? +

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

Can I rate-limit export_adom_config? +

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

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

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

KEEP EXPLORING

More on Fortimanager, and thousands of servers like it.

This server

All 584 Fortimanager tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →