Low Risk

list_available_firmware

list_available_firmware

How to control list_available_firmware ↓

What list_available_firmware does on Fortimanager

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

Low Risk

Why list_available_firmware needs a policy

The tool retrieves or enumerates available firmware versions—a read-only operation with no side effects. The empty description lowers confidence slightly, but the naming convention and context (FortiManager firmware management) clearly indicates this fetches data rather than applies or executes actions. Severity is low because firmware listings pose minimal risk even if disclosed or misused by an AI agent.

From the tool's definition Tool name 'list_available_firmware' indicates a query/listing operation that retrieves firmware information without modifying or executing anything.

Documented attack patterns abuse exactly the kind of access list_available_firmware gives an agent:

How to control list_available_firmware

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_available_firmware:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_available_firmware": {}
  }
}

list_available_firmware is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Fortimanager — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_available_firmware

What does the list_available_firmware tool do? +

list_available_firmware. 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 list_available_firmware? +

Register the Fortimanager MCP server in PolicyLayer and add a rule for list_available_firmware: 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 list_available_firmware? +

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

Can I rate-limit list_available_firmware? +

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

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

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

Enforce policy on every Fortimanager tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.