add_vdom
A write tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/add-vdom.md
What add_vdom does on Fortimanager
AI agents use add_vdom 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 add_vdom is rated Medium
The tool likely adds a VDOM (Virtual Domain) configuration object to FortiManager, which is a reversible operation that modifies system state but does not permanently delete data or execute arbitrary commands. The high severity reflects that VDOMs are fundamental network security constructs, so misuse could significantly impact network segmentation and security policies.
From the tool's definition Tool name 'add_vdom' indicates creating or adding a virtual domain to FortiManager; sibling tools like 'add_device_to_group', 'add_interface_to_zone', 'add_policies_to_block', and 'add_template_to_group' all perform reversible modifications to FortiManager…
Attacks that exploit this kind of access
The rule that runs add_vdom 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 add_vdom, this is the rule to start with:
add_vdom 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 add_vdom call is checked against it from then on.
Questions about add_vdom
add_vdom 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 add_vdom: 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.
add_vdom 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 add_vdom 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 add_vdom. 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.
add_vdom 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