AI agents call list_device_revisions 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 'list_device_revisions' tool appears to retrieve or enumerate revisions of a device, which is a read-only operation with no side effects. This falls squarely into the Read category. No destructive, financial, or execution capabilities are indicated. Severity is low because listing historical revisions poses minimal risk—an attacker cannot alter data or trigger unintended consequences through enumeration alone.
From the tool's definition Tool name 'list_device_revisions' uses the 'list' verb, indicating a query/retrieval operation. Description is empty, but the name strongly suggests reading revision history rather than modifying or executing actions.
Documented attack patterns abuse exactly the kind of access list_device_revisions 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 list_device_revisions:
{
"version": "1",
"default": "deny",
"tools": {
"list_device_revisions": {}
}
}list_device_revisions 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.
list_device_revisions. 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 list_device_revisions: 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.
list_device_revisions 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_device_revisions 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_device_revisions. 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_device_revisions 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.