clone_adom

A write tool on the Fortimanager MCP server.

SERVERFortimanager SOURCEjmpijll/fortimanager-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What clone_adom does on Fortimanager

AI agents use clone_adom to create or update resources in Fortimanager, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fortimanager environment.

RISK

Why clone_adom is rated Medium

Cloning an ADOM (Administrative Domain) in FortiManager would create a copy of an administrative domain, which is a Write operation. ADOMs can contain large numbers of policies, devices, and configurations, so misuse could have a high blast radius. However, confidence is reduced because the description is empty and we are inferring behavior from the name alone.

From the tool's definition Tool name 'clone_adom' suggests cloning an ADOM (Administrative Domain) in FortiManager. Description is empty, providing no additional context.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

clone_adom Rate-limited

clone_adom stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "clone_adom": {
      "limits": [
        {
          "counter": "clone_adom_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about clone_adom

What does the clone_adom tool do? +

clone_adom is a write tool on the Fortimanager MCP server. It is categorised as a Write tool in the Fortimanager MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on clone_adom? +

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

clone_adom is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit clone_adom? +

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

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

clone_adom 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

Govern customer-ops agents →Argument validation →Scoped token →