diff_device_revision

A read tool on the FortiManager MCP server.

SERVERFortiManager MCP Server SOURCErstierli/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/rstierli-fortimanager-mcp/diff-device-revision.md

WHAT IT DOES

What diff_device_revision does on FortiManager MCP Server

AI agents call diff_device_revision to retrieve information from FortiManager MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why diff_device_revision is rated Low

Tool name suggests comparing device revisions for inspection, likely read-only operation with minimal risk.

From the tool's definition uninformative description

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs diff_device_revision safely

PolicyLayer is an MCP gateway: it sits between your AI agents and FortiManager MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For diff_device_revision, this is the rule to start with:

diff_device_revision Allowed

diff_device_revision 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": {
    "diff_device_revision": {}
  }
}

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

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

FAQ

Questions about diff_device_revision

What does the diff_device_revision tool do? +

diff_device_revision is a read tool on the FortiManager MCP Server MCP server. It is categorised as a Read tool in the FortiManager MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on diff_device_revision? +

Register the FortiManager MCP Server MCP server in PolicyLayer and add a rule for diff_device_revision: 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 MCP Server. Nothing to install.

What risk level is diff_device_revision? +

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

Can I rate-limit diff_device_revision? +

Yes. Add a rate_limit block to the diff_device_revision 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 diff_device_revision completely? +

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

diff_device_revision is provided by the FortiManager MCP Server MCP server (rstierli/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 MCP Server, and thousands of servers like it.

This server

All 236 FortiManager MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

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