This record as markdown: /tools/jmpijll-fortimanager-mcp/delete-traffic-class.md
What delete_traffic_class does on Fortimanager
AI agents call delete_traffic_class 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_traffic_class is rated Critical
The tool performs an irreversible deletion of a traffic class configuration in FortiManager. Deletion of network traffic classes cannot be undone and affects network policy enforcement. While not as critical as deletion of all policies or firewall rules, removing a traffic class impacts quality-of-service and traffic management configurations, justifying 'high' severity.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a traffic class.' This is an irreversible deletion operation.
Attacks that exploit this kind of access
The rule that runs delete_traffic_class 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_traffic_class, this is the rule to start with:
delete_traffic_class 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_traffic_class call is checked against it from then on.
Questions about delete_traffic_class
Delete a traffic class. 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_traffic_class: 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_traffic_class 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_traffic_class 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_traffic_class. 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_traffic_class 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