delete_cli_script
A destructive tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/delete-cli-script.md
What delete_cli_script does on Fortimanager
AI agents call delete_cli_script to permanently remove resources in Fortimanager, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_cli_script is rated Critical
Deletion operations are inherently destructive and irreversible. Removing CLI scripts from a network management platform like FortiManager can disrupt operational workflows, disable critical automation, and cause service degradation. The lack of a description lowers confidence slightly, but the name alone is sufficiently explicit.
From the tool's definition Tool name is 'delete_cli_script' which explicitly indicates deletion of scripts. The verb 'delete' combined with 'script' indicates irreversible removal of configuration or automation artifacts from FortiManager.
Attacks that exploit this kind of access
The rule that runs delete_cli_script safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fortimanager, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_cli_script, this is the rule to start with:
delete_cli_script 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 Fortimanager, apply this rule, and every delete_cli_script call is checked against it from then on.
Questions about delete_cli_script
delete_cli_script is a destructive tool on the Fortimanager MCP server. It is categorised as a Destructive tool in the Fortimanager MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Fortimanager MCP server in PolicyLayer and add a rule for delete_cli_script: 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. Nothing to install.
delete_cli_script 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_cli_script 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_cli_script. 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_cli_script is provided by the Fortimanager MCP server (jmpijll/fortimanager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Fortimanager, and thousands of servers like it.
Across the catalogue