This record as markdown: /tools/jmpijll-fortimanager-mcp/list-ip-pools.md
What list_ip_pools does on Fortimanager
AI agents call list_ip_pools 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 list_ip_pools is rated Low
This tool performs a simple information retrieval operation on IP pool configurations within an ADOM (Administrative Domain). It has no side effects, does not modify data, and does not execute code or trigger external operations. The blast radius of misuse is low—an attacker could enumerate IP pools but cannot modify, delete, or abuse them through this tool alone.
From the tool's definition Tool name 'list_ip_pools' and description 'List all IP pools in an ADOM' indicate a read-only operation that retrieves and queries IP pool data without modification.
Attacks that exploit this kind of access
The rule that runs list_ip_pools 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 list_ip_pools, this is the rule to start with:
list_ip_pools 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 list_ip_pools call is checked against it from then on.
Questions about list_ip_pools
List all IP pools in an ADOM. 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_ip_pools: 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_ip_pools 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_ip_pools 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_ip_pools. 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_ip_pools 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