connect_device · PicoScope MCP Server MCP: Risk & Policy

WHAT IT DOES

What connect_device does on PicoScope MCP Server

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

WHY IT NEEDS A POLICY

Why connect_device needs a policy

Connecting to a device establishes a new connection/session state — a reversible write-like operation that creates a resource binding. It does not read data, execute code, destroy data, or involve finances. The blast radius is medium since misuse could monopolize the device or interfere with other users, but the action is reversible (see sibling tool disconnect_device).

From the tool's definition Connect to a specific PicoScope device

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_device Rate-limited

connect_device 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_device": {
      "limits": [
        {
          "counter": "connect_device_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 PicoScope MCP Server, so you can run agents against it safely.

FAQ

Questions about connect_device

What does the connect_device tool do? +

Connect to a specific PicoScope device. It is categorised as a Write tool in the PicoScope 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_device? +

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

What risk level is connect_device? +

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

Can I rate-limit connect_device? +

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

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

connect_device is provided by the PicoScope MCP Server MCP server (markuskreitzer/picoscope_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.