# create_adom_with_device_assignment A write tool on the Fortimanager MCP server. Agent View of the PolicyLayer registry record for `create_adom_with_device_assignment`. HTML page: https://policylayer.com/tools/jmpijll-fortimanager-mcp/create-adom-with-device-assignment ## Facts - Tool: `create_adom_with_device_assignment` - Server: Fortimanager (`jmpijll/fortimanager-mcp`) — https://policylayer.com/tools/jmpijll-fortimanager-mcp.md - Homepage: https://github.com/jmpijll/fortimanager-mcp - Risk category: Write (Medium risk) - Registry record: grade F, identity unverified - Server rate-limited: no - Parameters: 0 - Recommended policy verdict: Rate-limited ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "create_adom_with_device_assignment", "arguments": {} } } ``` ## 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 own 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." ## Use case 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. ## Recommended policy (PolicyLayer) Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Fortimanager: ```json { "version": "1", "default": "deny", "tools": { "create_adom_with_device_assignment": { "limits": [ { "counter": "create_adom_with_device_assignment_rate", "window": "minute", "max": 30, "scope": "grant" } ] } } } ``` ## Other tools on Fortimanager (583) - `bulk_delete_security_profile_entries` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/bulk-delete-security-profile-entries.md - `clear_database_cache` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/clear-database-cache.md - `delete_adom_revision` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-adom-revision.md - `delete_central_dnat_policy` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-central-dnat-policy.md - `delete_central_snat_policy` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-central-snat-policy.md - `delete_certificate_template` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-certificate-template.md - `delete_cli_script` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-cli-script.md - `delete_cli_template` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-cli-template.md - `delete_cli_template_group` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-cli-template-group.md - `delete_custom_application` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-custom-application.md - `delete_device_blueprint` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-device-blueprint.md - `delete_device_group` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-device-group.md - `delete_dns_filter_domain` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-dns-filter-domain.md - `delete_dynamic_interface` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-dynamic-interface.md - `delete_external_threat_feed` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-external-threat-feed.md - `delete_firewall_address` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-firewall-address.md - `delete_firewall_policy` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-firewall-policy.md - `delete_firewall_zone` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-firewall-zone.md - `delete_fortiap_profile` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-fortiap-profile.md - `delete_fortiextender` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-fortiextender.md - `delete_internet_service_fqdn` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-internet-service-fqdn.md - `delete_internet_service_group` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-internet-service-group.md - `delete_ip_pool` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-ip-pool.md - `delete_ips_sensor` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-ips-sensor.md - `delete_ipsec_phase1_interface` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-ipsec-phase1-interface.md - `delete_ipsec_phase2_interface` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-ipsec-phase2-interface.md - `delete_ipsec_template` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-ipsec-template.md - `delete_meta_field` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-meta-field.md - `delete_object_metadata` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-object-metadata.md - `delete_policy_block` — Destructive — https://policylayer.com/tools/jmpijll-fortimanager-mcp/delete-policy-block.md - …and 553 more: https://policylayer.com/tools/jmpijll-fortimanager-mcp.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=jmpijll-fortimanager-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/jmpijll-fortimanager-mcp