validate_policy_package
Validate policy package before installation to check for errors.
This record as markdown: /tools/jmpijll-fortimanager-mcp/validate-policy-package.md
What validate_policy_package does on Fortimanager
AI agents call validate_policy_package 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 validate_policy_package is rated Low
Validation tools read and analyze existing configuration to report issues; they do not modify, execute, or delete data. The blast radius is low since misuse would at worst produce a misleading validation result, not cause system changes.
From the tool's definition 'Validate policy package before installation to check for errors' — this is a pre-flight check that reads/analyzes the policy package for errors without making changes.
Attacks that exploit this kind of access
The rule that runs validate_policy_package 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 validate_policy_package, this is the rule to start with:
validate_policy_package 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 validate_policy_package call is checked against it from then on.
Questions about validate_policy_package
Validate policy package before installation to check for errors. 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 validate_policy_package: 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.
validate_policy_package 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 validate_policy_package 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 validate_policy_package. 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.
validate_policy_package 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