This record as markdown: /tools/takashito-linode-mcp-server/delete-firewall.md
What delete_firewall does on Linode MCP Server
AI agents call delete_firewall to permanently remove resources in Linode MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_firewall is rated Critical
Deleting a firewall is a destructive action that cannot be undone and removes network security controls. This has high blast radius if triggered by an AI agent without authorization, as it could expose infrastructure to unauthorized access. The action is irreversible, placing it in the Destructive category with high severity.
From the tool's definition Tool name is 'delete_firewall' with description 'Delete a firewall'. The verb 'delete' indicates irreversible removal of a security resource.
Attacks that exploit this kind of access
The rule that runs delete_firewall safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Linode MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_firewall, this is the rule to start with:
delete_firewall is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Linode MCP Server, apply this rule, and every delete_firewall call is checked against it from then on.
Questions about delete_firewall
Delete a firewall. It is categorised as a Destructive tool in the Linode MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Linode MCP Server MCP server in PolicyLayer and add a rule for delete_firewall: 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 Linode MCP Server. Nothing to install.
delete_firewall 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 delete_firewall 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 delete_firewall. 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.
delete_firewall is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Linode MCP Server, and thousands of servers like it.
Across the catalogue