find_policy_by_name

Find firewall policy by name instead of ID.

SERVERFortimanager SOURCEjmpijll/fortimanager-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/jmpijll-fortimanager-mcp/find-policy-by-name.md

WHAT IT DOES

What find_policy_by_name does on Fortimanager

AI agents call find_policy_by_name 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.

RISK

Why find_policy_by_name is rated Low

This is a read-only lookup function that searches for and returns firewall policy data by name. It has no side effects, does not execute code, does not modify data, and does not delete anything. The blast radius of misuse is minimal—an agent could only gain visibility into existing policies, not change system configuration or behavior.

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 state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs find_policy_by_name 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 find_policy_by_name, this is the rule to start with:

find_policy_by_name Allowed

find_policy_by_name is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_policy_by_name": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Fortimanager, apply this rule, and every find_policy_by_name call is checked against it from then on.

FAQ

Questions about find_policy_by_name

What does the find_policy_by_name tool do? +

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.

How do I enforce a policy on find_policy_by_name? +

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.

What risk level is find_policy_by_name? +

find_policy_by_name is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit find_policy_by_name? +

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.

How do I block find_policy_by_name completely? +

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.

What MCP server provides find_policy_by_name? +

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.

KEEP EXPLORING

More on Fortimanager, and thousands of servers like it.

This server

All 584 Fortimanager tools →

Across the catalogue

get_cocktail_by_name on Cocktails RAG MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →