network-ls
Lists Docker networks with structured driver and scope information.
This record as markdown: /tools/io-github-dave-london-go/network-ls.md
What network-ls does on Go
AI agents call network-ls to retrieve information from Go without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why network-ls is rated Low
This tool retrieves and displays information about Docker networks in a structured format. It performs a read-only operation that queries existing infrastructure state without creating, modifying, deleting, or executing code. The blast radius of misuse is minimal—an agent could only discover network topology information, which may have some minor information disclosure risk but no operational impact.
From the tool's definition Tool name 'network-ls' and description 'Lists Docker networks' indicate a query/listing operation with no modification or deletion of resources.
Attacks that exploit this kind of access
The rule that runs network-ls safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Go, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For network-ls, this is the rule to start with:
network-ls is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Go, apply this rule, and every network-ls call is checked against it from then on.
Questions about network-ls
Lists Docker networks with structured driver and scope information. It is categorised as a Read tool in the Go MCP Server, which means it retrieves data without modifying state.
Register the Go MCP server in PolicyLayer and add a rule for network-ls: 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 Go. Nothing to install.
network-ls is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the network-ls 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 network-ls. 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.
network-ls is provided by the Go MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Go, and thousands of servers like it.
This server
Across the catalogue