scope_query · LeCroy Oscilloscope MCP: Risk & Policy

WHAT IT DOES

What scope_query does on LeCroy Oscilloscope MCP

AI agents invoke scope_query 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_query needs a policy

The description is empty, lowering confidence. However, given the server context (SCPI command-based remote control of lab equipment) and the 'query' naming convention in SCPI contexts (which typically sends raw commands that can both read and configure instrument state), this tool likely executes arbitrary SCPI commands.

From the tool's definition Tool name 'scope_query' on a server that 'Enables remote control of LeCroy oscilloscopes via SCPI commands'; sibling tools include scope_arm, scope_calibrate, scope_configure_channel, scope_configure_trigger, suggesting this tool may send arbitrary SCPI…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scope_query Rate-limited

scope_query 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_query": {
      "limits": [
        {
          "counter": "scope_query_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_query

What does the scope_query tool do? +

scope_query. 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_query? +

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

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

Can I rate-limit scope_query? +

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

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

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