get_configuration_changes
Get recent configuration changes for audit trail.
This record as markdown: /tools/jmpijll-fortimanager-mcp/get-configuration-changes.md
What get_configuration_changes does on Fortimanager
AI agents call get_configuration_changes 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_configuration_changes is rated Low
This tool retrieves historical configuration change data for auditing purposes. It performs a read-only query against FortiManager's audit trail, returning information without modifying, executing, or deleting anything. The low severity reflects minimal blast radius—an AI agent misusing this tool would only expose audit information, not compromise system integrity or operations.
From the tool's definition Tool name is 'get_configuration_changes' and description states 'Get recent configuration changes for audit trail' — the verb 'Get' and purpose of retrieving audit information indicates data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs get_configuration_changes 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_configuration_changes, this is the rule to start with:
get_configuration_changes 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_configuration_changes call is checked against it from then on.
Questions about get_configuration_changes
Get recent configuration changes for audit trail. 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_configuration_changes: 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_configuration_changes 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_configuration_changes 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_configuration_changes. 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_configuration_changes 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