AI agents call measure_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.
This tool acquires and measures waveform data from an oscilloscope, which is a read-only operation. It retrieves voltage/timing measurements without creating, modifying, deleting, or destructively changing any data. The 'adaptive acquisition' and 'measurement suite' are analytical features that process captured data. No side effects or irreversible actions are possible.
From the tool's definition Tool name is "measure_waveform" and description states "adaptive acquisition with full measurement suite." Both indicate data retrieval and analysis operations on oscilloscope readings with no modification of underlying system state or configuration.
Attacks that exploit this kind of access
Same as read_waveform — adaptive acquisition with full measurement suite. 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 measure_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.
measure_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 measure_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 measure_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.
measure_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 →