# get_fabric_connector_devices A read tool on the Fortimanager MCP server. Agent View of the PolicyLayer registry record for `get_fabric_connector_devices`. HTML page: https://policylayer.com/tools/jmpijll-fortimanager-mcp/get-fabric-connector-devices ## Facts - Tool: `get_fabric_connector_devices` - Server: Fortimanager (`jmpijll/fortimanager-mcp`) — https://policylayer.com/tools/jmpijll-fortimanager-mcp.md - Homepage: https://github.com/jmpijll/fortimanager-mcp - Risk category: Read (Low risk) - Registry record: grade F, identity unverified - Server rate-limited: no - Parameters: 0 - Recommended policy verdict: Allowed ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "get_fabric_connector_devices", "arguments": {} } } ``` ## Why get_fabric_connector_devices is rated Low Based on the naming convention alone, 'get_' typically indicates a read operation that retrieves information about fabric connector devices without modification. However, low confidence is assigned because the description is empty and uninformative. Without concrete details about what data is returned or any side effects, there is elevated uncertainty. From the tool's own definition: "Tool name 'get_fabric_connector_devices' begins with 'get', which suggests a retrieval operation. The description is empty, providing no additional context to confirm or refute this classification." ## Use case AI agents call get_fabric_connector_devices to retrieve information from Fortimanager without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere. ## Recommended policy (PolicyLayer) Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Fortimanager: ```json { "version": "1", "default": "deny", "tools": { "get_fabric_connector_devices": {} } } ``` ## 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