菜单
Discover and classify OT / IoT / IoMT assets via Claroty xDome. List devices by site, Purdue level, and device purpose; assign Purdue layers and custom attributes; cross-reference with Nautobot / NetBox SoT to surface drift.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | claroty-asset-inventory |
| description | Discover and classify OT / IoT / IoMT assets via Claroty xDome. List devices by site, Purdue level, and device purpose; assign Purdue layers and custom attributes; cross-reference with Nautobot / NetBox SoT to surface drift. |
| license | Apache-2.0 |
| user-invocable | true |
| metadata | {"openclaw":{"requires":{"bins":["python3"],"env":["CLAROTY_API_URL","CLAROTY_API_TOKEN"]}}} |
OT / IoT / IoMT asset discovery, Purdue Model classification, and source-of-truth reconciliation, using the Claroty xDome MCP server.
claroty-mcp (in-repo, mcp-servers/claroty-mcp/claroty_mcp_server.py)python3 -u mcp-servers/claroty-mcp/claroty_mcp_server.py (stdio transport)CLAROTY_API_TOKENCHG\d+); bypassed in NETCLAW_LAB_MODE=true| Tool | Parameters | What It Does |
|---|---|---|
list_devices | site_id?, purdue_level?, device_purpose?, name_contains?, limit?, offset?, max_items? | List xDome-managed devices with rich filters |
get_device_details | device_id | Full record for a single device including raw attributes |
set_device_purdue_level | device_id, purdue_level, cr_number | Write (ITSM-gated) — assign Purdue layer |
set_device_custom_attribute | device_id, attribute_key, attribute_value, cr_number | Write (ITSM-gated) — set a custom attribute |
For cross-referencing, also reach for:
nautobot_get_ip_address / nautobot_get_prefix from the nautobot-sot skillnetbox-reconcile from the NetBox skills"List the first 50 devices at site warehouse-east at Purdue level 1, showing names, vendors, and risk scores"
Calls list_devices(site_id="warehouse-east", purdue_level="Level 1", limit=50). Returns a GCF-encoded device table.
"List all PLCs across all sites"
Calls list_devices(device_purpose="PLC", max_items=500).
"Set device 7a2c... to Purdue level 2 under CHG0012345"
Calls set_device_purdue_level(device_id="7a2c...", purdue_level="Level 2", cr_number="CHG0012345"). The ITSM gate validates the CR before the POST.
"Compare xDome devices at site warehouse-east to Nautobot's inventory for that site and flag anything missing on either side"
list_devices(site_id="warehouse-east") → xDome setnautobot_get_ip_address(...) filtered by site → SoT set"Mark device 9f4d... with custom attribute compliance_scope=PCI under CHG0012999"
Calls set_device_custom_attribute(device_id="9f4d...", attribute_key="compliance_scope", attribute_value="PCI", cr_number="CHG0012999").
All write tools call validate_change_request(cr_number) from mcp-servers/claroty-mcp/utils/itsm_gate.py. The CR must:
CHG\d+.NETCLAW_LAB_MODE=true).A rejection returns {"itsm_gate": {...}, "applied": false} and the xDome call is NOT made.
If set_device_purdue_level or set_device_custom_attribute returns applied: false and an error object with status_code: 403, the ITSM gate passed and the request body is correct — xDome rejected at RBAC. The token in CLAROTY_API_TOKEN lacks write scope on devices. Don't retry — escalate to whoever provisions xDome API tokens.
Every tool invocation is recorded in GAIT. The audit trail includes the tool name, parameters, CR number (for writes), and the xDome response status.
Federate your NetClaw with other NetClaw operators over the BGP mesh — exchange capability inventories and ask your claw what a peer can do. (US1; remote invocation and chat land in later phases.)
Catalyst Center device inventory and site management - list/filter devices by hostname, IP, platform, family, role, reachability; view site hierarchy; get interface details per device; device reachability monitoring; cross-reference with pyATS. Use when listing network devices, checking device reachability, auditing software versions, viewing site hierarchy, or finding a device by serial number.
Catalyst Center troubleshooting workflows - device unreachable investigation, client connectivity issues, interface down analysis, site-wide outage triage, wireless roaming problems, integration with pyATS for CLI-level diagnostics. Use when a device is unreachable, a user reports connectivity problems, an interface is down, a site has an outage, or wireless clients have roaming issues.
Human-in-the-loop escalation via HumanRail — route low-confidence agent decisions, pre-destructive operation approvals, and ambiguous incident tickets to real human engineers. Human answers are verified and returned as structured output. Workers are paid via Lightning Network. Use when the agent is uncertain, when a destructive change needs explicit human sign-off beyond a ServiceNow CR, or when an ambiguous ticket requires human triage before automated handling.
Generate and manage Visio network diagrams on SharePoint via Microsoft Graph API - create topology diagrams from CDP/LLDP discovery, update existing diagrams, export to PDF. Use when creating Visio topology diagrams, uploading network diagrams to SharePoint, or generating physical/logical topology views from discovery data
Reconcile NetBox source of truth against live network state - detect IP drift, missing interfaces, undocumented links, cable mismatches, VLAN mismatches, and ticket discrepancies in ServiceNow. Use when validating NetBox accuracy, checking for config drift, auditing network documentation, or reconciling source of truth after changes