Network tools
此内容尚不支持你的语言。
Container networks and what is attached to each.
Permission is what the tool server requires before it dispatches; who holds it is read from the control plane’s own grant. The two are read from different places on purpose: a tool server that grants more than the control plane does offers an operation and then has it refused halfway through a conversation.
Advertised says whether the tool appears in the default tool list. Most do not:
a small window is advertised and the rest are found with search_tools, read with
describe_tool and invoked with request_tool. A tool reached that way is checked
against the same permission as a direct call.
Generated from Tool. Hand edits to this table are overwritten on the next build — change the Go doc comment, or the generator.
| Tool | Permission | Who holds it | Advertised |
|---|---|---|---|
network_connect |
networks:manage |
operator |
no |
network_create |
networks:manage |
operator |
no |
network_delete |
networks:manage |
operator |
no |
network_disconnect |
networks:manage |
operator |
no |
network_inspect |
networks:read |
developer, operator, readonly, support |
no |
network_list |
networks:read |
developer, operator, readonly, support |
no |
network_connect
Section titled “network_connect”Connect a container to a Docker network
| Argument | Type | Required | Meaning |
|---|---|---|---|
network |
string |
yes | Network name or ID |
container_id |
string |
yes | Container ID or name to connect |
network_create
Section titled “network_create”Create a new Docker network with optional IPAM configuration
| Argument | Type | Required | Meaning |
|---|---|---|---|
name |
string |
yes | Name for the new network |
driver |
one of bridge, overlay, macvlan |
no | Network driver (default: bridge) |
subnet |
string |
no | Subnet in CIDR format (e.g., ‘172.20.0.0/16’) |
gateway |
string |
no | Gateway IP address (e.g., ‘172.20.0.1’) |
internal |
boolean |
no | Restrict external access to the network |
attachable |
boolean |
no | Enable manual container attachment |
network_delete
Section titled “network_delete”Delete a Docker network. Will fail if containers are connected unless force is used.
| Argument | Type | Required | Meaning |
|---|---|---|---|
name |
string |
yes | Network name or ID to delete |
force |
boolean |
no | Force deletion by disconnecting all containers first |
confirm |
boolean |
yes | Must be true to proceed with network deletion |
network_disconnect
Section titled “network_disconnect”Disconnect a container from a Docker network
| Argument | Type | Required | Meaning |
|---|---|---|---|
network |
string |
yes | Network name or ID |
container_id |
string |
yes | Container ID or name to disconnect |
force |
boolean |
no | Force disconnection even if container is running |
confirm |
boolean |
yes | Must be true. Disconnecting a container from a network can sever its connectivity to everything it depends on. |
network_inspect
Section titled “network_inspect”Get detailed information about a specific Docker network including IPAM config and connected containers
| Argument | Type | Required | Meaning |
|---|---|---|---|
name |
string |
yes | Network name or ID |
network_list
Section titled “network_list”List all Docker networks with their configuration and connected containers. Use format=‘summary’ (default) for minimal output, ‘standard’ for operational details, or ‘full’ for complete data. Use network_inspect for full details on a specific network.
| Argument | Type | Required | Meaning |
|---|---|---|---|
driver |
one of bridge, host, overlay, macvlan, none |
no | Filter by network driver type |
format |
one of summary, standard, full |
no | Response detail level: ‘summary’ (minimal), ‘standard’ (operational), ‘full’ (complete). Default: summary |