Permanently delete a project and all its files.
AI agents call gns3_delete_project to permanently remove resources in GNS3 Network Simulator MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes an entire project and all associated files with no undo capability. While the blast radius is typically limited to a single simulation project rather than production systems, the permanent and complete nature of the operation, combined with the potential loss of complex network topology configurations, justifies 'high' severity.
From the tool's definition Tool name 'gns3_delete_project' and description 'Permanently delete a project and all its files' explicitly indicate irreversible deletion of data.
Documented attack patterns abuse exactly the kind of access gns3_delete_project gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GNS3 Network Simulator MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for gns3_delete_project:
{
"version": "1",
"default": "deny",
"hide": [
"gns3_delete_project"
]
}gns3_delete_project disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Permanently delete a project and all its files. It is categorised as a Destructive tool in the GNS3 Network Simulator MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GNS3 Network Simulator MCP Server MCP server in PolicyLayer and add a rule for gns3_delete_project: 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 GNS3 Network Simulator MCP Server. Nothing to install.
gns3_delete_project is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the gns3_delete_project 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 gns3_delete_project. 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.
gns3_delete_project is provided by the GNS3 Network Simulator MCP Server MCP server (wael-rd/gns3-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GNS3 Network Simulator 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.
42 GNS3 Network Simulator MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.