create_adom_with_device_assignment

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/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.

Questions about create_adom_with_device_assignment

What does the create_adom_with_device_assignment tool do? +

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.

How do I enforce a policy on create_adom_with_device_assignment? +

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.

What risk level is create_adom_with_device_assignment? +

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

Can I rate-limit create_adom_with_device_assignment? +

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.

How do I block create_adom_with_device_assignment completely? +

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.

What MCP server provides create_adom_with_device_assignment? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Fortimanager's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.