create_adom_with_device_assignment
A write tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/create-adom-with-device-assignment.md
What create_adom_with_device_assignment does on Fortimanager
AI agents use create_adom_with_device_assignment 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 create_adom_with_device_assignment is rated Medium
The 'create' verb indicates this tool creates new configuration entities (ADOM) and modifies assignments reversibly. This is a Write operation—it creates or modifies data that can be undone. Severity is medium because an adversary could create unauthorized administrative domains and assign devices, potentially establishing unauthorized management structures, but this does not directly delete data or move money.
From the tool's definition Tool name includes 'create_adom_with_device_assignment' which indicates creation of an administrative domain (adom) and assignment of devices. No description provided; classification based on the 'create' action in the name.
Attacks that exploit this kind of access
The rule that runs create_adom_with_device_assignment 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 create_adom_with_device_assignment, this is the rule to start with:
create_adom_with_device_assignment 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 create_adom_with_device_assignment call is checked against it from then on.
Questions about create_adom_with_device_assignment
create_adom_with_device_assignment 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 create_adom_with_device_assignment: 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.
create_adom_with_device_assignment 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 create_adom_with_device_assignment 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 create_adom_with_device_assignment. 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.
create_adom_with_device_assignment 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