AI agents call query_fortiguard_outbreak to retrieve information from Fortimanager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve threat intelligence or outbreak information from FortiGuard (Fortinet's threat intelligence service). The 'query' prefix and context of FortiManager suggest this fetches read-only security threat data. However, confidence is reduced to 0.7 because the description is empty, preventing confirmation of whether there are any side effects.
From the tool's definition Tool name 'query_fortiguard_outbreak' uses 'query' prefix, indicating data retrieval. FortiGuard Outbreak Intelligence is a threat intelligence service that provides information about active security threats and outbreaks.
Documented attack patterns abuse exactly the kind of access query_fortiguard_outbreak 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 query_fortiguard_outbreak:
{
"version": "1",
"default": "deny",
"tools": {
"query_fortiguard_outbreak": {}
}
}query_fortiguard_outbreak is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
query_fortiguard_outbreak. It is categorised as a Read tool in the Fortimanager MCP Server, which means it retrieves data without modifying state.
Register the Fortimanager MCP server in PolicyLayer and add a rule for query_fortiguard_outbreak: 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.
query_fortiguard_outbreak 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 query_fortiguard_outbreak 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 query_fortiguard_outbreak. 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.
query_fortiguard_outbreak 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.