validate_policy_package_errors
Validate policy package configuration for errors.
This record as markdown: /tools/jmpijll-fortimanager-mcp/validate-policy-package-errors.md
What validate_policy_package_errors does on Fortimanager
AI agents call validate_policy_package_errors 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_errors is rated Low
This tool performs validation and error-checking on policy package configurations. Validation is inherently a read-only operation that retrieves and analyzes configuration state to report errors, with no side effects, data modification, or external execution. The severity is low because misuse would only result in incorrect validation results, not damage to systems or data.
From the tool's definition Tool name 'validate_policy_package_errors' and description 'Validate policy package configuration for errors' indicate a validation/checking operation that inspects existing configuration without modifying, deleting, or executing external actions.
Attacks that exploit this kind of access
The rule that runs validate_policy_package_errors 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_errors, this is the rule to start with:
validate_policy_package_errors 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_errors call is checked against it from then on.
Questions about validate_policy_package_errors
Validate policy package configuration 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_errors: 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_errors 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_errors 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_errors. 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_errors 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