usbtmc_screenshot_keysight_display

Capture screenshot from a Keysight/Agilent oscilloscope.

Server USBTMC MCP Server naonaome/usbtmc-lite-mcp
Category Read
Risk class Low
Parameters 00 required

What usbtmc_screenshot_keysight_display does on USBTMC MCP Server

AI agents call usbtmc_screenshot_keysight_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.

Why usbtmc_screenshot_keysight_display needs a policy

Taking a screenshot is a non-destructive query operation that retrieves visual data from the device without altering its configuration, measurements, or stored data. It has minimal blast radius—the worst outcome is exposure of displayed information. This is clearly a Read operation rather than Write (no modifications), Execute (no commands run), Destructive, or Financial.

From the tool's definition Tool name 'usbtmc_screenshot_keysight_display' and description 'Capture screenshot from a Keysight/Agilent oscilloscope' indicate a retrieval operation with no modification or side effects on the device's state or data.

Questions about usbtmc_screenshot_keysight_display

What does the usbtmc_screenshot_keysight_display tool do? +

Capture screenshot from a Keysight/Agilent oscilloscope. It is categorised as a Read tool in the USBTMC MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on usbtmc_screenshot_keysight_display? +

Register the USBTMC MCP Server MCP server in PolicyLayer and add a rule for usbtmc_screenshot_keysight_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.

What risk level is usbtmc_screenshot_keysight_display? +

usbtmc_screenshot_keysight_display is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit usbtmc_screenshot_keysight_display? +

Yes. Add a rate_limit block to the usbtmc_screenshot_keysight_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.

How do I block usbtmc_screenshot_keysight_display completely? +

Set action: deny in the PolicyLayer policy for usbtmc_screenshot_keysight_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.

What MCP server provides usbtmc_screenshot_keysight_display? +

usbtmc_screenshot_keysight_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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.