disconnect_device · PicoScope MCP Server MCP: Risk & Policy

WHAT IT DOES

What disconnect_device does on PicoScope MCP Server

AI agents use disconnect_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 disconnect_device needs a policy

Disconnecting a device is a Write operation because it modifies the state of the system (changes the device connection from connected to disconnected). It is reversible—the device can be reconnected via the 'connect_device' tool. It does not destroy data, execute arbitrary code, move money, or have irreversible side effects, so it warrants low severity.

From the tool's definition Tool name 'disconnect_device' and description 'Disconnect from the currently connected PicoScope device' indicate a reversible state change operation that modifies the connection status of a device.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

disconnect_device Rate-limited

disconnect_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": {
    "disconnect_device": {
      "limits": [
        {
          "counter": "disconnect_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 disconnect_device

What does the disconnect_device tool do? +

Disconnect from the currently connected 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 disconnect_device? +

Register the PicoScope MCP Server MCP server in PolicyLayer and add a rule for disconnect_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 disconnect_device? +

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

Can I rate-limit disconnect_device? +

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

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

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