AI agents use connect_node_to_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 modifies network topology by establishing a connection between two nodes in the EVE-NG emulation environment. While it changes the state of the lab configuration, it is reversible—connections can be removed or reconfigured. It does not execute arbitrary commands, delete data permanently, or move financial assets.
From the tool's definition Tool name 'connect_node_to_node' and description 'Connect two nodes together directly' indicate a network topology modification that creates a link between nodes.
Documented attack patterns abuse exactly the kind of access connect_node_to_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 connect_node_to_node:
{
"version": "1",
"default": "deny",
"tools": {
"connect_node_to_node": {
"limits": [
{
"counter": "connect_node_to_node_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} connect_node_to_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.
Connect two nodes together directly. 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 connect_node_to_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.
connect_node_to_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 connect_node_to_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 connect_node_to_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.
connect_node_to_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.