network-ls
Lists Docker networks with structured driver and scope information.
This record as markdown: /tools/io-github-dave-london-pare-test/network-ls.md
What network-ls does on Test
AI agents call network-ls to retrieve information from Test 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 returns information about Docker networks in a structured format. It performs a read-only operation with no side effects—it does not create, modify, delete, or execute commands. The blast radius of misuse is minimal; an agent obtaining network topology information presents lower risk than tools that can modify infrastructure or execute arbitrary commands.
From the tool's definition Tool name 'network-ls' and description 'Lists Docker networks with structured driver and scope information' indicate a query/list operation that retrieves network metadata without modifying, executing against, or deleting networks.
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 Test, 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 Test, 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 Test MCP Server, which means it retrieves data without modifying state.
Register the Test 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 Test. 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 Test 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 Test, and thousands of servers like it.
This server
Across the catalogue