AI agents call list_lab_networks to retrieve information from EVE-NG MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that retrieves data about networks within a lab. It has no side effects, does not modify, delete, or execute any operations. The verb 'list' is characteristic of Read category tools. Even in a network emulation context, listing configurations poses minimal risk as it only exposes information already present in the system.
From the tool's definition Tool name 'list_lab_networks' and description 'List all networks in a lab' indicate a query operation that retrieves and displays existing network information without modifying state.
Documented attack patterns abuse exactly the kind of access list_lab_networks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and EVE-NG MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_lab_networks:
{
"version": "1",
"default": "deny",
"tools": {
"list_lab_networks": {}
}
}list_lab_networks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all networks in a lab. It is categorised as a Read tool in the EVE-NG MCP Server MCP Server, which means it retrieves data without modifying state.
Register the EVE-NG MCP Server MCP server in PolicyLayer and add a rule for list_lab_networks: 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 EVE-NG MCP Server. Nothing to install.
list_lab_networks 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 list_lab_networks 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 list_lab_networks. 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.
list_lab_networks is provided by the EVE-NG MCP Server MCP server (moimran/eveng-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from EVE-NG MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
26 EVE-NG MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.