delete_address_group
AI agents call delete_address_group 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.
Deletion of address groups in a centralized firewall policy management system cannot be undone and will immediately affect firewall rules that reference the deleted group. This is a destructive operation with potential to disrupt network security configurations.
From the tool's definition Tool name 'delete_address_group' explicitly indicates deletion of a network address group object. The verb 'delete' is a destructive operation that irreversibly removes configuration data from FortiManager.
Attacks that exploit this kind of access
delete_address_group. 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.
Register the FortiManager MCP Server MCP server in PolicyLayer and add a rule for delete_address_group: 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.
delete_address_group 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_address_group 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_address_group. 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_address_group 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.
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 →