Search bounded traffic logs by fields such as srcip, dstip, policyid, service, action, or dstport.
AI agents call fortigate_search_traffic_logs 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.
This tool retrieves and searches existing traffic log data without side effects. It is a typical read/query operation that inspects firewall logs for security analysis and monitoring purposes. The read-only nature of the server and the bounded search parameters confirm no write, execute, or destructive capabilities exist.
From the tool's definition Tool name includes 'search' and description states it queries traffic logs by fields (srcip, dstip, policyid, service, action, dstport). Server description explicitly states 'read-only querying and diagnostics'.
Attacks that exploit this kind of access
Search bounded traffic logs by fields such as srcip, dstip, policyid, service, action, or dstport. 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_search_traffic_logs: 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_search_traffic_logs 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_search_traffic_logs 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_search_traffic_logs. 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_search_traffic_logs 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 →