Return DNAT/VIP, VIP groups, IP pools, central SNAT, and firewall NAT policy references.
AI agents call fortigate_get_nat_overview to retrieve information from Fortigate MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves firewall NAT configuration data without modifying, executing, or deleting anything. It is a diagnostic/inspection operation aligned with the read-only nature of the Fortigate MCP server. The blast radius of misuse is limited to information disclosure about NAT policies, which poses low risk.
From the tool's definition Tool returns/retrieves NAT configuration overview (DNAT/VIP, VIP groups, IP pools, central SNAT, firewall NAT policy references). Description uses 'return' indicating data retrieval.
Attacks that exploit this kind of access
Return DNAT/VIP, VIP groups, IP pools, central SNAT, and firewall NAT policy references. It is categorised as a Read tool in the Fortigate MCP MCP Server, which means it retrieves data without modifying state.
Register the Fortigate MCP server in PolicyLayer and add a rule for fortigate_get_nat_overview: 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 Fortigate MCP. Nothing to install.
fortigate_get_nat_overview 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 fortigate_get_nat_overview 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 fortigate_get_nat_overview. 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.
fortigate_get_nat_overview is provided by the Fortigate MCP server (picaresco/mcp-fortigate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →