Skip to main content
Glama
paoloamato2

FortiOS 7.6.x MCP Server

by paoloamato2

firewall_policy_list

Query IPv4 firewall policies with filters by interfaces, action, or VDOM, returning policy ID, name, addresses, services, and status.

Instructions

List IPv4 firewall policies with optional filters.

Returns policy ID, name, source/destination interfaces and zones, source/destination addresses, services, action, and status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startNoOffset for pagination.
countNoMax number of policies to return.
filter_srcintfNoFilter by source interface name.
filter_dstintfNoFilter by destination interface name.
filter_actionNoFilter by action: accept or deny.
vdomNoTarget VDOM name. Defaults to the server default VDOM. Use '*' for all VDOMs (super-admin required).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so the description is the sole source for behavioral traits. It states returned fields but does not disclose that the operation is read-only, pagination behavior, or any side effects. Adequate but could be improved.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with action and resource, with no extraneous information. Every sentence serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists, the description need not detail return values. It covers core purpose and available filters. Pagination could be explicitly mentioned, but overall complete for a list tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and parameter descriptions in the schema are clear. The description adds little beyond stating optional filters. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The tool name and description clearly state it lists IPv4 firewall policies. It distinguishes from sibling tools like firewall_policy6_list (IPv6) and firewall_policy_get (single policy). The description includes returned fields, reinforcing purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions optional filters but does not provide explicit guidance on when to use this tool versus alternatives such as firewall_policy_get or monitor tools. Usage context is implied but not clearly specified.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/paoloamato2/fortinet-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server