Return DoS policies, traffic shapers, and per-IP shapers that can drop or rate-limit traffic.
AI agents call fortigate_get_traffic_controls to retrieve information from Fortigate MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although the underlying policies CAN drop or rate-limit traffic, this tool merely RETRIEVES or INSPECTS those policies—it does not execute, apply, or modify them. The action is purely informational. Misuse (e.g., an agent reading this data) poses minimal risk compared to tools that would actually modify or apply traffic controls. Classification is Read, consistent with the server's read-only security posture.
From the tool's definition Tool name and description indicate retrieval of existing DoS policies, traffic shapers, and per-IP shapers ('Return' and 'get'). The server is explicitly described as 'read-only querying and diagnostics' with 'no side effects' capability.
Attacks that exploit this kind of access
Return DoS policies, traffic shapers, and per-IP shapers that can drop or rate-limit traffic. It is categorised as a Read tool in the Fortigate MCP MCP Server, which means it retrieves data without modifying state.
Register the Fortigate MCP server in PolicyLayer and add a rule for fortigate_get_traffic_controls: 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 Fortigate MCP. Nothing to install.
fortigate_get_traffic_controls is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the fortigate_get_traffic_controls 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 fortigate_get_traffic_controls. 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.
fortigate_get_traffic_controls is provided by the Fortigate MCP server (picaresco/mcp-fortigate). 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 →