AI agents call preview_policy_install_single as a supporting operation in Fortimanager workflows.
The description is empty, so we cannot confirm the actual behavior. The name 'preview' typically implies a read/dry-run operation with no side effects. However, given sibling tools like 'abort_policy_install' exist, this could be part of a policy installation workflow. Classifying as Other/Read with low confidence due to empty description; 'preview' implies read-only but cannot be certain.
From the tool's definition Tool name 'preview_policy_install_single' and empty description. Name suggests a preview/read operation before policy install.
Documented attack patterns abuse exactly the kind of access preview_policy_install_single 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 preview_policy_install_single:
{
"version": "1",
"default": "deny",
"tools": {
"preview_policy_install_single": {
"limits": [
{
"counter": "preview_policy_install_single_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
} preview_policy_install_single gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
preview_policy_install_single. It is categorised as a Other tool in the Fortimanager MCP Server, which means it performs auxiliary operations.
Register the Fortimanager MCP server in PolicyLayer and add a rule for preview_policy_install_single: 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.
preview_policy_install_single is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the preview_policy_install_single 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 preview_policy_install_single. 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.
preview_policy_install_single 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.