scope_save_waveform_csv
AI agents use scope_save_waveform_csv to create or update resources in LeCroy Oscilloscope MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LeCroy Oscilloscope MCP environment.
The tool creates or exports a new CSV file containing waveform data from the oscilloscope. This is a Write operation because it creates new data artifacts on the system (the CSV file). It is reversible—the file can be deleted or overwritten.
From the tool's definition Tool name 'scope_save_waveform_csv' indicates saving/exporting waveform data to a CSV file. The server description mentions 'waveform capture' and the sibling tools include functions like 'scope_capture_channels' and 'scope_configure_trigger', establishing…
Attacks that exploit this kind of access
scope_save_waveform_csv. It is categorised as a Write tool in the LeCroy Oscilloscope MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LeCroy Oscilloscope MCP server in PolicyLayer and add a rule for scope_save_waveform_csv: 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_save_waveform_csv is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the scope_save_waveform_csv 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_save_waveform_csv. 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_save_waveform_csv 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 →