AI agents call get_central_snat_policy 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.
This is a read-only query operation that retrieves SNAT policy information from FortiManager. It has no side effects and does not modify, execute, or destroy data. The low severity reflects that information disclosure about firewall policies, while potentially sensitive in a real deployment, poses minimal direct risk compared to tools that can modify security policies or execute commands.
From the tool's definition Tool name contains 'get' and description states 'Get central SNAT policy details' — pure retrieval of existing configuration data with no modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access get_central_snat_policy gives an agent:
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 get_central_snat_policy:
{
"version": "1",
"default": "deny",
"tools": {
"get_central_snat_policy": {}
}
}get_central_snat_policy is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get central SNAT policy details. 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 get_central_snat_policy: 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.
get_central_snat_policy 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 get_central_snat_policy 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 get_central_snat_policy. 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.
get_central_snat_policy 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.
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.