scope_set_trigger_delay · LeCroy Oscilloscope MCP

WHAT IT DOES

What scope_set_trigger_delay does on LeCroy Oscilloscope MCP

AI agents use scope_set_trigger_delay 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.

WHY IT NEEDS A POLICY

Why scope_set_trigger_delay needs a policy

This tool modifies the oscilloscope's trigger delay/horizontal position offset setting. It is a configuration write operation that changes instrument state. It is reversible (the delay can be changed back), so it falls under Write rather than Destructive. Misuse could affect ongoing measurements but poses no data loss or financial risk.

From the tool's definition Set the trigger delay (horizontal position offset)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scope_set_trigger_delay Rate-limited

scope_set_trigger_delay stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_set_trigger_delay": {
      "limits": [
        {
          "counter": "scope_set_trigger_delay_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_set_trigger_delay

What does the scope_set_trigger_delay tool do? +

Set the trigger delay (horizontal position offset). 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.

How do I enforce a policy on scope_set_trigger_delay? +

Register the LeCroy Oscilloscope MCP server in PolicyLayer and add a rule for scope_set_trigger_delay: 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_set_trigger_delay? +

scope_set_trigger_delay is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit scope_set_trigger_delay? +

Yes. Add a rate_limit block to the scope_set_trigger_delay 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_set_trigger_delay completely? +

Set action: deny in the PolicyLayer policy for scope_set_trigger_delay. 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_set_trigger_delay? +

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