AI agents call traffic_delete_pipe to permanently remove resources in OPNSense MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a traffic shaper pipe, an infrastructure component. Deletion of network configuration cannot be undone without manual reconfiguration. While not as critical as deleting firewall rules wholesale, removing traffic shaping pipes disrupts QoS and network performance controls. The Destructive category applies because the action is irreversible and affects network operations.
From the tool's definition Tool name contains 'delete' and description states 'Delete a traffic shaper pipe' — irreversible removal of network traffic configuration.
Documented attack patterns abuse exactly the kind of access traffic_delete_pipe gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OPNSense MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for traffic_delete_pipe:
{
"version": "1",
"default": "deny",
"hide": [
"traffic_delete_pipe"
]
}traffic_delete_pipe 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.
Delete a traffic shaper pipe. It is categorised as a Destructive tool in the OPNSense MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OPNSense MCP Server MCP server in PolicyLayer and add a rule for traffic_delete_pipe: 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 OPNSense MCP Server. Nothing to install.
traffic_delete_pipe 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 traffic_delete_pipe 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 traffic_delete_pipe. 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.
traffic_delete_pipe is provided by the OPNSense MCP Server MCP server (vespo92/opnsensemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 196 OPNSense MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
196 OPNSense MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.