Check whether the server has an active VISA connection and identify the scope.
AI agents call scope_connection_status to retrieve information from LeCroy Oscilloscope MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves connection state and identification information about the oscilloscope. It performs no operations, modifications, code execution, or destructive actions. It is a simple diagnostic read operation with minimal security impact even if misused by an AI agent.
From the tool's definition Tool description states it 'Check[s] whether the server has an active VISA connection and identify[s] the scope' - purely a status query with no side effects.
Attacks that exploit this kind of access
Check whether the server has an active VISA connection and identify the scope. It is categorised as a Read tool in the LeCroy Oscilloscope MCP MCP Server, which means it retrieves data without modifying state.
Register the LeCroy Oscilloscope MCP server in PolicyLayer and add a rule for scope_connection_status: 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 LeCroy Oscilloscope MCP. Nothing to install.
scope_connection_status 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 scope_connection_status 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 scope_connection_status. 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.
scope_connection_status is provided by the LeCroy Oscilloscope MCP server (lucasgerads/lecroy-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 →