AI agents call delete_device_blueprint 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.
Deletion operations are inherently destructive and cannot be undone. Removing a device blueprint from FortiManager is a permanent action that eliminates configuration templates and could disrupt device management workflows. The blast radius is high because accidental or malicious deletion of critical blueprints could affect multiple devices and require manual recovery or reconfiguration.
From the tool's definition Tool name is 'delete_device_blueprint' with description 'Delete a device blueprint.' The verb 'delete' indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete_device_blueprint gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fortimanager, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_device_blueprint:
{
"version": "1",
"default": "deny",
"hide": [
"delete_device_blueprint"
]
}delete_device_blueprint disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a device blueprint. 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_device_blueprint: 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_device_blueprint 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_device_blueprint 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_device_blueprint. 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_device_blueprint 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.
Start from Fortimanager, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
584 Fortimanager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.