delete_security_profile_group

Delete a security profile group.

SERVERFortimanager SOURCEjmpijll/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/jmpijll-fortimanager-mcp/delete-security-profile-group.md

What delete_security_profile_group does on Fortimanager

AI agents call delete_security_profile_group 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_security_profile_group is rated Critical

Deletion of security profile groups is an irreversible operation that cannot be undone and represents destructive action on network security configuration. While not immediately causing financial loss or code execution, the removal of security controls could have cascading impacts on system protection. This is more severe than Write operations (which are reversible) and clearly Destructive in nature.

From the tool's definition Tool name contains 'delete'; description states 'Delete a security profile group' - irreversible deletion of a configuration object

Questions about delete_security_profile_group

What does the delete_security_profile_group tool do? +

Delete a security profile group. 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.

How do I enforce a policy on delete_security_profile_group? +

Register the Fortimanager MCP server in PolicyLayer and add a rule for delete_security_profile_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. Nothing to install.

What risk level is delete_security_profile_group? +

delete_security_profile_group 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_security_profile_group? +

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

How do I block delete_security_profile_group completely? +

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

What MCP server provides delete_security_profile_group? +

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

// 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'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.