scope_decode_read
AI agents call scope_decode_read 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.
The 'read' suffix strongly suggests this tool retrieves or decodes waveform data from the oscilloscope rather than modifying device state or triggering operations. Within the context of oscilloscope control, 'decode' likely refers to interpreting captured waveform data (protocol decoding, measurements) rather than executing commands.
From the tool's definition Tool name 'scope_decode_read' contains 'read' which typically indicates data retrieval. Server context shows oscilloscope measurement and waveform capture operations.
Attacks that exploit this kind of access
scope_decode_read. 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_decode_read: 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_decode_read 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_decode_read 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_decode_read. 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_decode_read 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 →