scope_measure
AI agents call scope_measure to retrieve information from Oscilloscope without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'scope_measure' strongly suggests it performs measurement readings from an oscilloscope (e.g., frequency, voltage, amplitude). Measurement operations are typically read-only, querying instrument data without side effects. However, the description is empty, which lowers confidence. Given the server context of waveform capture and frequency measurements, this is most likely a Read operation.
From the tool's definition Tool name 'scope_measure' on a server described as enabling 'waveform capture, CSV export, and frequency measurements' on an oscilloscope.
Attacks that exploit this kind of access
scope_measure. It is categorised as a Read tool in the Oscilloscope MCP Server, which means it retrieves data without modifying state.
Register the Oscilloscope MCP server in PolicyLayer and add a rule for scope_measure: 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 Oscilloscope. Nothing to install.
scope_measure 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_measure 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_measure. 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_measure is provided by the Oscilloscope MCP server (sandraschi/oscilloscope-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 →