validate_cli_template
A execute tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/validate-cli-template.md
What validate_cli_template does on Fortimanager
AI agents invoke validate_cli_template to trigger actions in Fortimanager. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why validate_cli_template is rated High
Based on the tool name, this appears to validate a CLI template, which likely involves executing or parsing CLI commands against FortiManager. In the context of FortiManager and sibling tools that modify network configurations, CLI template validation could trigger execution of commands. However, the empty description significantly lowers confidence.
From the tool's definition Tool name 'validate_cli_template' suggests execution of CLI template validation; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs validate_cli_template 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_cli_template, this is the rule to start with:
validate_cli_template stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_cli_template call is checked against it from then on.
Questions about validate_cli_template
validate_cli_template is a execute tool on the Fortimanager MCP server. It is categorised as a Execute tool in the Fortimanager MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Fortimanager MCP server in PolicyLayer and add a rule for validate_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.
validate_cli_template is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the validate_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 validate_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.
validate_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.
More on Fortimanager, and thousands of servers like it.
Across the catalogue