scope_calibrate · LeCroy Oscilloscope MCP: Risk & Policy

WHAT IT DOES

What scope_calibrate does on LeCroy Oscilloscope MCP

AI agents invoke scope_calibrate to trigger actions in LeCroy Oscilloscope MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why scope_calibrate needs a policy

The tool executes a calibration procedure on the oscilloscope, which is an operational command that affects the instrument's measurement accuracy and state. While not destructive (calibration is reversible and expected behavior), it goes beyond read operations and constitutes an active execute-class action.

From the tool's definition Tool performs 'self-calibration (*CAL?)' which triggers an external calibration operation on the oscilloscope hardware. This is an active operation that modifies instrument state and behavior.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scope_calibrate Rate-limited

scope_calibrate stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "scope_calibrate": {
      "limits": [
        {
          "counter": "scope_calibrate_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches LeCroy Oscilloscope MCP, so you can run agents against it safely.

FAQ

Questions about scope_calibrate

What does the scope_calibrate tool do? +

Run self-calibration (*CAL?) and return the result status. It is categorised as a Execute tool in the LeCroy Oscilloscope MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on scope_calibrate? +

Register the LeCroy Oscilloscope MCP server in PolicyLayer and add a rule for scope_calibrate: 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.

What risk level is scope_calibrate? +

scope_calibrate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit scope_calibrate? +

Yes. Add a rate_limit block to the scope_calibrate 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.

How do I block scope_calibrate completely? +

Set action: deny in the PolicyLayer policy for scope_calibrate. 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.

What MCP server provides scope_calibrate? +

scope_calibrate 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.