This record as markdown: /tools/0xnullai-dg-mcp/disconnect.md
What disconnect does on DG-MCP
AI agents use disconnect to create or update resources in DG-MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DG-MCP environment.
Why disconnect is rated Medium
Disconnecting a device is a reversible action (the device can be reconnected), so it falls under Write rather than Destructive. However, in the context of a DG-Lab Coyote electrostimulation device, unexpected disconnection could have physical safety implications, raising the severity to medium. It does not delete data or execute arbitrary code.
From the tool's definition 断开设备连接 (disconnect device connection) — disconnects a specific or all connected devices
Attacks that exploit this kind of access
The rule that runs disconnect safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DG-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For disconnect, this is the rule to start with:
disconnect 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.
The button opens the PolicyLayer dashboard: create your workspace, connect DG-MCP, apply this rule, and every disconnect call is checked against it from then on.
Questions about disconnect
断开设备连接。指定 address 则只断开该设备,省略则断开全部已连接设备。. It is categorised as a Write tool in the DG-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DG MCP server in PolicyLayer and add a rule for disconnect: 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 DG-MCP. Nothing to install.
disconnect is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the disconnect 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.
Set action: deny in the PolicyLayer policy for disconnect. 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.
disconnect is provided by the DG MCP server (0xnullai/dg-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DG, and thousands of servers like it.
This server
Across the catalogue