bulk_delete_security_profile_entries
AI agents call bulk_delete_security_profile_entries 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.
The tool name explicitly indicates bulk deletion of security profile entries, which is an irreversible action that destroys data. Even without a description, 'delete' combined with 'bulk' and 'security_profile_entries' clearly fits the Destructive category. The high severity reflects the potential to remove multiple critical security configurations at once, affecting network defense posture.
From the tool's definition Tool name contains 'delete' and 'bulk', indicating irreversible removal of security profile entries. No description provided, but sibling tools like 'add_policies_to_block', 'add_ips_rule' suggest this server manages FortiManager security configurations where…
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access bulk_delete_security_profile_entries 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 bulk_delete_security_profile_entries:
{
"version": "1",
"default": "deny",
"hide": [
"bulk_delete_security_profile_entries"
]
} bulk_delete_security_profile_entries 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.
bulk_delete_security_profile_entries. 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 bulk_delete_security_profile_entries: 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.
bulk_delete_security_profile_entries 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 bulk_delete_security_profile_entries 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 bulk_delete_security_profile_entries. 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.
bulk_delete_security_profile_entries 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.