explore_scpi · Instrument MCP Server MCP: Risk & Policy

WHAT IT DOES

What explore_scpi does on Instrument MCP Server

AI agents invoke explore_scpi to trigger actions in Instrument MCP Server. 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 explore_scpi needs a policy

SCPI (Standard Commands for Programmable Instruments) commands execute operations on physical test equipment. Exploring SCPI likely sends commands to instruments, which can change their state or configuration. The description is empty, reducing confidence, but the server context strongly implies execution of instrument commands. Misuse could misconfigure or damage physical equipment, hence high severity.

From the tool's definition Tool name 'explore_scpi' on a server that 'Enables natural language control of test instruments via SCPI commands' — SCPI commands are sent to physical instruments (spectrum analyzers, power supplies) and can trigger real-world effects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

explore_scpi Rate-limited

explore_scpi 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": {
    "explore_scpi": {
      "limits": [
        {
          "counter": "explore_scpi_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 Instrument MCP Server, so you can run agents against it safely.

FAQ

Questions about explore_scpi

What does the explore_scpi tool do? +

explore_scpi. It is categorised as a Execute tool in the Instrument MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on explore_scpi? +

Register the Instrument MCP Server MCP server in PolicyLayer and add a rule for explore_scpi: 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 Instrument MCP Server. Nothing to install.

What risk level is explore_scpi? +

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

Can I rate-limit explore_scpi? +

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

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

explore_scpi is provided by the Instrument MCP Server MCP server (zeng-andrew/instrument-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.