New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_package

A destructive tool on the FortiManager MCP server.

SERVERFortiManager MCP Server SOURCErstierli/fortimanager-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/rstierli-fortimanager-mcp/delete-package.md

What delete_package does on FortiManager MCP Server

AI agents call delete_package to permanently remove resources in FortiManager MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_package is rated Critical

The verb 'delete' combined with the context of firewall policy management indicates an irreversible destructive action. Firewall packages represent critical security configurations; their deletion would disrupt network protection and require administrative remediation. While the description is empty, the tool name is explicit and the blast radius is significant (high severity).

From the tool's definition Tool name 'delete_package' combined with FortiManager context (centralized firewall policy management) indicates permanent removal of firewall configuration packages.

Questions about delete_package

What does the delete_package tool do? +

delete_package is a destructive tool on the FortiManager MCP Server MCP server. It is categorised as a Destructive tool in the FortiManager 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 delete_package? +

Register the FortiManager MCP Server MCP server in PolicyLayer and add a rule for delete_package: 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 FortiManager MCP Server. Nothing to install.

What risk level is delete_package? +

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

Yes. Add a rate_limit block to the delete_package 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 delete_package completely? +

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

delete_package is provided by the FortiManager MCP Server MCP server (rstierli/fortimanager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on FortiManager MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of FortiManager MCP Server's. Pull the full record:

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.