Close a device session and free its resources.
AI agents use disconnect to create or update resources in Network Device Assistant — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Network Device Assistant environment.
Disconnecting a session modifies the state of the network device assistant by closing an established connection and freeing resources. This is reversible (a session can be re-established via connect_serial or connect_ssh), so it does not qualify as Destructive. It is not Execute because the tool itself does not run arbitrary commands on the device.
From the tool's definition Tool name 'disconnect' and description 'Close a device session and free its resources' indicate a modification to system state—specifically terminating an active connection and deallocating resources.
Attacks that exploit this kind of access
Close a device session and free its resources. It is categorised as a Write tool in the Network Device Assistant MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Network Device Assistant 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 Network Device Assistant. 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 Network Device Assistant MCP server (mgarabito/network-device-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →