list_central_dnat_policies
A read tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/list-central-dnat-policies.md
What list_central_dnat_policies does on Fortimanager
AI agents call list_central_dnat_policies 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_central_dnat_policies is rated Low
The 'list_' prefix is a strong indicator of a Read operation that queries and retrieves data. DNAT (Destination Network Address Translation) policy listing would retrieve existing security configuration settings without modifying, deleting, or executing anything. The blast radius of misuse is low—an attacker could enumerate policies but cannot modify firewall rules or cause operational harm through enumeration alone.
From the tool's definition Tool name 'list_central_dnat_policies' uses the verb 'list', which retrieves or queries data without side effects. The description is empty, but naming conventions strongly indicate this is a read-only operation that returns a list of existing DNAT policies.
Attacks that exploit this kind of access
The rule that runs list_central_dnat_policies 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_central_dnat_policies, this is the rule to start with:
list_central_dnat_policies 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_central_dnat_policies call is checked against it from then on.
Questions about list_central_dnat_policies
list_central_dnat_policies is a read tool on the Fortimanager MCP server. 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_central_dnat_policies: 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_central_dnat_policies 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_central_dnat_policies 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_central_dnat_policies. 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_central_dnat_policies 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