list_account_history
List account history entries for the FortiMonitor account.
This record as markdown: /tools/gjenkins20-unofficial-fortimonitor-mcp-server/list-account-history.md
What list_account_history does on Unofficial FortiMonitor MCP Server
AI agents call list_account_history to retrieve information from Unofficial FortiMonitor MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_account_history is rated Low
This tool queries and returns historical account data without modifying, deleting, or executing any operations. It has no capability to change account state, trigger actions, or cause irreversible changes. The blast radius of misuse is limited to potential exposure of historical account information, which is a low-severity concern in a monitoring context.
From the tool's definition Tool name 'list_account_history' and description 'List account history entries' indicate a retrieval operation with no side effects. The verb 'list' is characteristic of read-only queries.
Attacks that exploit this kind of access
The rule that runs list_account_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unofficial FortiMonitor MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_account_history, this is the rule to start with:
list_account_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 Unofficial FortiMonitor MCP Server, apply this rule, and every list_account_history call is checked against it from then on.
Questions about list_account_history
List account history entries for the FortiMonitor account. It is categorised as a Read tool in the Unofficial FortiMonitor MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Unofficial FortiMonitor MCP Server MCP server in PolicyLayer and add a rule for list_account_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 Unofficial FortiMonitor MCP Server. Nothing to install.
list_account_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 list_account_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 list_account_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.
list_account_history is provided by the Unofficial FortiMonitor MCP Server MCP server (gjenkins20/unofficial-fortimonitor-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Unofficial FortiMonitor MCP Server, and thousands of servers like it.
Across the catalogue