AI agents use create_traffic_class to create or update resources in Fortimanager — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fortimanager environment.
This tool creates (writes) a new traffic classification rule/object in FortiManager, which affects network traffic handling and security policy. While reversible via deletion, it modifies system configuration with potential impact on network operations. It does not execute arbitrary code, delete data irreversibly, or move money, so Write is appropriate.
From the tool's definition Tool name 'create_traffic_class' and description 'Create a traffic class' indicate data creation. This creates a new traffic class object in FortiManager, a network security management system.
Documented attack patterns abuse exactly the kind of access create_traffic_class 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 create_traffic_class:
{
"version": "1",
"default": "deny",
"tools": {
"create_traffic_class": {
"limits": [
{
"counter": "create_traffic_class_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_traffic_class stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a traffic class. It is categorised as a Write tool in the Fortimanager MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fortimanager MCP server in PolicyLayer and add a rule for create_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.
create_traffic_class is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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.
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.