get_alert_history

Get system alert history.

SERVERFortimanager SOURCEjmpijll/fortimanager-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/jmpijll-fortimanager-mcp/get-alert-history.md

WHAT IT DOES

What get_alert_history does on Fortimanager

AI agents call get_alert_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.

RISK

Why get_alert_history is rated Low

This tool retrieves historical alert data from FortiManager without modifying, executing, or deleting anything. It is a straightforward query operation with minimal blast radius if misused by an agent—at worst, an agent could retrieve large volumes of alert logs, causing performance issues, but no actual system state changes occur.

From the tool's definition Tool name 'get_alert_history' and description 'Get system alert history' indicate a retrieval operation with no data modification or external effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_alert_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_alert_history, this is the rule to start with:

get_alert_history Allowed

get_alert_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_alert_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Fortimanager, apply this rule, and every get_alert_history call is checked against it from then on.

FAQ

Questions about get_alert_history

What does the get_alert_history tool do? +

Get system alert history. It is categorised as a Read tool in the Fortimanager MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_alert_history? +

Register the Fortimanager MCP server in PolicyLayer and add a rule for get_alert_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.

What risk level is get_alert_history? +

get_alert_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_alert_history? +

Yes. Add a rate_limit block to the get_alert_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.

How do I block get_alert_history completely? +

Set action: deny in the PolicyLayer policy for get_alert_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.

What MCP server provides get_alert_history? +

get_alert_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.

KEEP EXPLORING

More on Fortimanager, and thousands of servers like it.

This server

All 584 Fortimanager tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →