AI agents call find_policy_by_name 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 tool performs a lookup operation to retrieve firewall policy data based on a name parameter. It has no side effects—it only reads and returns existing policy information. This is a classic Read category tool. Severity is low because discovery of policy names poses minimal risk; the actual enforcement of policies or modification of firewall rules requires separate tools.
From the tool's definition Tool name 'find_policy_by_name' and description 'Find firewall policy by name instead of ID' indicate a query/search operation that retrieves policy information without modifying or executing actions.
Documented attack patterns abuse exactly the kind of access find_policy_by_name 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 find_policy_by_name:
{
"version": "1",
"default": "deny",
"tools": {
"find_policy_by_name": {}
}
}find_policy_by_name 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.
Find firewall policy by name instead of ID. 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 find_policy_by_name: 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.
find_policy_by_name 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 find_policy_by_name 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 find_policy_by_name. 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.
find_policy_by_name 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.