Validate policy package before installation to check for errors.
AI agents call validate_policy_package 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.
The tool performs validation and checking of policy packages—a read-only operation that retrieves and analyzes information without creating, modifying, deleting, or executing any configurations. The term 'validate' combined with 'check for errors' confirms this is an informational audit function. The blast radius is minimal since validation produces no side effects.
From the tool's definition Tool name 'validate_policy_package' and description 'Validate policy package before installation to check for errors' indicate a validation/check operation with no modification of data or execution of policies.
Documented attack patterns abuse exactly the kind of access validate_policy_package 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 validate_policy_package:
{
"version": "1",
"default": "deny",
"tools": {
"validate_policy_package": {}
}
}validate_policy_package 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.
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.
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.