AI agents call assign_prerun_cli_template as a supporting operation in Fortimanager workflows.
The description is empty, so the category must be inferred from the name alone. 'Assign_prerun_cli_template' suggests associating a CLI template to run before some operation on a device, which would be a Write action (creating/modifying a configuration association). However, since this involves CLI execution on network devices it could be Execute. Given the ambiguity and empty description, confidence is low.
From the tool's definition Tool name: assign_prerun_cli_template — description is empty and uninformative
Documented attack patterns abuse exactly the kind of access assign_prerun_cli_template 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 assign_prerun_cli_template:
{
"version": "1",
"default": "deny",
"tools": {
"assign_prerun_cli_template": {
"limits": [
{
"counter": "assign_prerun_cli_template_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
} assign_prerun_cli_template gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
assign_prerun_cli_template. 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 assign_prerun_cli_template: 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.
assign_prerun_cli_template 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 assign_prerun_cli_template 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 assign_prerun_cli_template. 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.
assign_prerun_cli_template 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.