AI agents call read_waveform to retrieve information from Niscope without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
read_waveform retrieves waveform data from an oscilloscope without altering state or configuration. This is a non-destructive query operation. Confidence is 0.85 rather than higher due to the empty tool description, but the naming convention and server context strongly support Read classification. No side effects, no data modification, no code execution, and no financial impact.
From the tool's definition Tool name 'read_waveform' indicates data retrieval from an oscilloscope. The server description shows this tool is part of waveform acquisition capabilities ('waveform acquisition, measurement, and configuration').
Attacks that exploit this kind of access
read_waveform. It is categorised as a Read tool in the Niscope MCP Server, which means it retrieves data without modifying state.
Register the Niscope MCP server in PolicyLayer and add a rule for read_waveform: 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 Niscope. Nothing to install.
read_waveform 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 read_waveform 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 read_waveform. 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.
read_waveform is provided by the Niscope MCP server (ymzds/niscope-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 →