connect · Instrument MCP Server MCP: Risk & Policy

WHAT IT DOES

What connect does on Instrument MCP Server

AI agents use connect to create or update resources in Instrument MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Instrument MCP Server environment.

WHY IT NEEDS A POLICY

Why connect needs a policy

With no description available, classification is inferred from context. 'connect' in an instrument control server likely establishes a session/connection to a physical instrument. This is a Write-level action (creating a session/connection state) rather than destructive or financial. However, connecting to physical instruments like power supplies could have real-world effects depending on subsequent commands.

From the tool's definition Tool name 'connect' with empty description; server context involves test instruments like spectrum analyzers and power supplies via SCPI commands with session support.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect Rate-limited

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

FAQ

Questions about connect

What does the connect tool do? +

connect. It is categorised as a Write tool in the Instrument MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on connect? +

Register the Instrument MCP Server MCP server in PolicyLayer and add a rule for connect: 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 connect? +

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

Can I rate-limit connect? +

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

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

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