tm_delete_tool

TMOS API DELETE. path는 삭제할 리소스까지 포함 (예: ltm/pool/~Common~my_pool).

Server F5 MCP Server mink0119/f5-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What tm_delete_tool does on F5 MCP Server

AI agents call tm_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.

Why tm_delete_tool needs a policy

This tool performs irreversible deletion of F5 network infrastructure objects (pools, virtual servers, etc.) via the iControl REST API. Misuse by an AI agent could permanently destroy critical load-balancing configurations, resulting in service outages and inability to undo changes. This meets the Destructive category definition as it cannot be undone and has critical blast radius in a network infrastructure context.

From the tool's definition Tool name 'tm_delete_tool' and description explicitly states 'TMOS API DELETE' with example showing deletion of resources like 'ltm/pool/~Common~my_pool'. DELETE operations irreversibly remove F5 configurations.

Questions about tm_delete_tool

What does the tm_delete_tool tool do? +

TMOS API DELETE. path는 삭제할 리소스까지 포함 (예: ltm/pool/~Common~my_pool). 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.

How do I enforce a policy on tm_delete_tool? +

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

What risk level is tm_delete_tool? +

tm_delete_tool 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 tm_delete_tool? +

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

How do I block tm_delete_tool completely? +

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

What MCP server provides tm_delete_tool? +

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.