AI agents invoke stop_node to trigger actions in EVE-NG MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a command against the EVE-NG emulation platform to halt a running node. While not destructive (the node state is reversible via restart), it triggers an external operation with side effects that cannot be undone without explicit action. The blast radius is medium because stopping a node could disrupt network simulations or lab exercises, but the effect is contained and reversible.
From the tool's definition Tool name 'stop_node' and description 'Stop a specific node' indicate triggering an external operation (stopping a network emulation node) whose effects depend on which node is targeted as an argument.
Documented attack patterns abuse exactly the kind of access stop_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 stop_node:
{
"version": "1",
"default": "deny",
"tools": {
"stop_node": {
"limits": [
{
"counter": "stop_node_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stop_node stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Stop a specific node. It is categorised as a Execute tool in the EVE-NG MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the EVE-NG MCP Server MCP server in PolicyLayer and add a rule for stop_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.
stop_node is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the stop_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 stop_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.
stop_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.