list_labs

THE RISK

Low Risk

Why list_labs needs a policy

This tool retrieves information about existing labs in the EVE-NG platform without modifying, deleting, or executing any operations. It is a straightforward informational read operation with minimal risk of unintended consequences.

From the tool's definition Tool name 'list_labs' and description 'List available labs in EVE-NG' indicate a query/retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access list_labs gives an agent:

POLICY

How to control list_labs

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_labs:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_labs": {}
  }
}

list_labs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register EVE-NG MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More EVE-NG MCP Server tools

Destructive delete_lab Delete a lab from EVE-NG. Destructive delete_lab_network Delete a network from a lab. Destructive delete_node Delete a node from a lab. Destructive wipe_all_nodes Wipe all nodes in a lab (reset to factory state). Destructive wipe_node Wipe a specific node (reset to factory state). Execute start_all_nodes Start all nodes in a lab. Execute start_node Start a specific node. Execute stop_all_nodes Stop all nodes in a lab.

All 26 EVE-NG MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about list_labs

What does the list_labs tool do? +

List available labs in EVE-NG. It is categorised as a Read tool in the EVE-NG MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_labs? +

Register the EVE-NG MCP Server MCP server in PolicyLayer and add a rule for list_labs: 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.

What risk level is list_labs? +

list_labs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_labs? +

Yes. Add a rate_limit block to the list_labs 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.

How do I block list_labs completely? +

Set action: deny in the PolicyLayer policy for list_labs. 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.

What MCP server provides list_labs? +

list_labs 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.

Enforce policy on every EVE-NG MCP Server tool call.

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.

CHECK YOUR STACK →