AI agents use add_node 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.
This tool creates (adds) a network node to an existing lab, which is a reversible modification operation. It does not execute arbitrary code, delete data permanently, transfer financial value, or read/query existing data—it creates new infrastructure configuration. Write is the appropriate category as the most severe applicable classification among its capabilities.
From the tool's definition Tool name 'add_node' and description 'Add a node to a lab' indicate creation of a new resource within the EVE-NG network emulation platform.
Documented attack patterns abuse exactly the kind of access add_node 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 add_node:
{
"version": "1",
"default": "deny",
"tools": {
"add_node": {
"limits": [
{
"counter": "add_node_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_node 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.
Add a node to a lab. 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 add_node: 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.
add_node 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 add_node 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 add_node. 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.
add_node 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.