리소스 삭제. resource_path 예: ltm/pool, net/vlan, net/self.
AI agents call delete_tool to permanently remove resources in F5 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 F5 network infrastructure objects (pools, VLANs, self IPs). Deletion cannot be undone and directly impacts production network availability. Blast radius is critical if an AI agent misuses this without proper validation, as it can remove essential load balancing, network routing, or interface configurations.
From the tool's definition Tool name is 'delete_tool' and description states '리소스 삭제' (resource deletion in Korean). Accepts 'resource_path' examples including 'ltm/pool', 'net/vlan', 'net/self' — all deletable F5 configuration objects.
Attacks that exploit this kind of access
리소스 삭제. resource_path 예: ltm/pool, net/vlan, net/self. It is categorised as a Destructive tool in the F5 MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the F5 MCP Server MCP server in PolicyLayer and add a rule for delete_tool: 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 F5 MCP Server. Nothing to install.
delete_tool 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_tool 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_tool. 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_tool is provided by the F5 MCP Server MCP server (mink0119/f5-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →