move_vdom_to_adom
A write tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/move-vdom-to-adom.md
What move_vdom_to_adom does on Fortimanager
AI agents use move_vdom_to_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.
Why move_vdom_to_adom is rated Medium
The tool performs a structural modification within FortiManager's domain hierarchy by moving a vdom to a different adom. This is a Write-category operation because it creates/modifies associations reversibly. The severity is high because misconfiguring domain assignments could disrupt network policy enforcement, device management hierarchies, and access controls across the infrastructure.
From the tool's definition Tool name 'move_vdom_to_adom' indicates it relocates a virtual domain (vdom) to an administrative domain (adom) within FortiManager. The 'move' operation modifies organizational structure and associations.
Attacks that exploit this kind of access
The rule that runs move_vdom_to_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 move_vdom_to_adom, this is the rule to start with:
move_vdom_to_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Fortimanager, apply this rule, and every move_vdom_to_adom call is checked against it from then on.
Questions about move_vdom_to_adom
move_vdom_to_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.
Register the Fortimanager MCP server in PolicyLayer and add a rule for move_vdom_to_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.
move_vdom_to_adom is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the move_vdom_to_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.
Set action: deny in the PolicyLayer policy for move_vdom_to_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.
move_vdom_to_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.
More on Fortimanager, and thousands of servers like it.
This server
Across the catalogue