AI agents use create_lab to create or update resources in EVE-NG MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EVE-NG MCP Server environment.
The tool creates new labs, a reversible operation that adds data to the EVE-NG system but does not execute arbitrary code, delete data, or move funds. The blast radius is medium because misconfigured labs could disrupt network emulation workflows, but the action is reversible via deletion. Write is the appropriate category as this is a standard create operation.
From the tool's definition Tool name is 'create_lab' and description states 'Create a new lab in EVE-NG', which creates new data structures (lab configurations) in the network emulation platform.
Documented attack patterns abuse exactly the kind of access create_lab 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 create_lab:
{
"version": "1",
"default": "deny",
"tools": {
"create_lab": {
"limits": [
{
"counter": "create_lab_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_lab stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new lab in EVE-NG. It is categorised as a Write tool in the EVE-NG MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the EVE-NG MCP Server MCP server in PolicyLayer and add a rule for create_lab: 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.
create_lab is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_lab 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 create_lab. 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.
create_lab 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.