get_fortiguard_update_history
A read tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/get-fortiguard-update-history.md
What get_fortiguard_update_history does on Fortimanager
AI agents call get_fortiguard_update_history to retrieve information from Fortimanager without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_fortiguard_update_history is rated Low
The 'get' prefix and 'history' suffix strongly suggest this tool queries historical information about FortiGuard updates without modifying, executing, or deleting anything. The empty description lowers confidence slightly, but the naming convention is sufficiently clear. This is a read-only operation typical of audit or status checking in security appliance management, with minimal blast radius if misused.
From the tool's definition Tool name 'get_fortiguard_update_history' uses the 'get' verb which indicates retrieval of historical data with no side effects.
Attacks that exploit this kind of access
The rule that runs get_fortiguard_update_history 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 get_fortiguard_update_history, this is the rule to start with:
get_fortiguard_update_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Fortimanager, apply this rule, and every get_fortiguard_update_history call is checked against it from then on.
Questions about get_fortiguard_update_history
get_fortiguard_update_history is a read tool on the Fortimanager MCP server. 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 get_fortiguard_update_history: 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.
get_fortiguard_update_history 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 get_fortiguard_update_history 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 get_fortiguard_update_history. 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.
get_fortiguard_update_history 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.
This server
Across the catalogue