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.
This tool modifies the assignment and grouping of virtual domains within administrative domains—a reversible but significant infrastructure change. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or involve financial transactions (would be Financial).
From the tool's definition Tool name 'move_vdom_to_adom' indicates moving/reassigning virtual domains to administrative domains in FortiManager, which modifies organizational structure and security policy assignments.
Documented attack patterns abuse exactly the kind of access move_vdom_to_adom gives an agent:
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 move_vdom_to_adom:
{
"version": "1",
"default": "deny",
"tools": {
"move_vdom_to_adom": {
"limits": [
{
"counter": "move_vdom_to_adom_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
move_vdom_to_adom. 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.
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.