Critical Risk →

delete_node

Delete a node from a lab.

How to control delete_node ↓

What delete_node does on EVE-NG MCP Server

AI agents call delete_node to permanently remove resources in EVE-NG MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_node needs a policy

This tool permanently removes a node from a lab topology. While the blast radius is contained to the lab environment (not affecting live production systems), deletion of nodes cannot be undone and represents a destructive action that irreversibly alters the lab configuration.

From the tool's definition Tool name is 'delete_node' and description states 'Delete a node from a lab.' The verb 'delete' indicates irreversible removal of an entity.

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

How to control delete_node

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_node"
  ]
}

delete_node disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_node

What does the delete_node tool do? +

Delete a node from a lab. It is categorised as a Destructive tool in the EVE-NG MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_node? +

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

What risk level is delete_node? +

delete_node is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_node? +

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

How do I block delete_node completely? +

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

What MCP server provides delete_node? +

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

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.

Free to start. No card required.

26 EVE-NG MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.