Capture screenshot from a Tektronix oscilloscope.
AI agents call usbtmc_screenshot_tektronix_display 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.
The tool name and description indicate it captures/retrieves display content (screenshot) from test equipment. This is a non-destructive read operation with no side effects—it queries the current display state without creating, modifying, deleting, or executing commands on the device.
From the tool's definition Tool performs screenshot capture from a Tektronix oscilloscope display—a read-only operation that retrieves visual data without modifying device state or triggering measurements.
Attacks that exploit this kind of access
Capture screenshot from a Tektronix oscilloscope. 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_screenshot_tektronix_display: 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_screenshot_tektronix_display 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_screenshot_tektronix_display 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_screenshot_tektronix_display. 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_screenshot_tektronix_display 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 →