usbtmc_list_connected_devices
AI agents call usbtmc_list_connected_devices to retrieve information from USBTMC MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about connected USBTMC devices without modifying state, executing commands, or deleting data. It is a read-only enumeration operation. Severity is low because even if misused, listing devices has minimal blast radius—no equipment is controlled, modified, or damaged.
From the tool's definition Tool name 'usbtmc_list_connected_devices' indicates it lists/enumerates devices; description is empty but sibling tool 'usbtmc_list_devices' in the same server context confirms this is a query operation.
Attacks that exploit this kind of access
usbtmc_list_connected_devices. It is categorised as a Read tool in the USBTMC MCP Server MCP Server, which means it retrieves data without modifying state.
Register the USBTMC MCP Server MCP server in PolicyLayer and add a rule for usbtmc_list_connected_devices: 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 USBTMC MCP Server. Nothing to install.
usbtmc_list_connected_devices is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the usbtmc_list_connected_devices 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 usbtmc_list_connected_devices. 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.
usbtmc_list_connected_devices is provided by the USBTMC MCP Server MCP server (naonaome/usbtmc-lite-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →