validate_template
A execute tool on the FortiManager MCP server.
This record as markdown: /tools/rstierli-fortimanager-mcp/validate-template.md
What validate_template does on FortiManager MCP Server
AI agents invoke validate_template to trigger actions in FortiManager MCP Server. 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_template is rated High
The description is empty, so classification is based on the tool name and server context. 'validate_template' likely triggers a validation process/execution against a template configuration on FortiManager, which is an active operation (Execute category). It is unlikely to be purely Read (no data retrieval implied) or Destructive/Financial. Confidence is low due to empty description.
From the tool's definition Tool name: validate_template; description is empty/uninformative. Inferred from context of sibling tools (assign_template, assign_system_template, etc.) on a FortiManager server managing firewall policies and network configuration.
Attacks that exploit this kind of access
The rule that runs validate_template safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FortiManager MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For validate_template, this is the rule to start with:
validate_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 MCP Server, apply this rule, and every validate_template call is checked against it from then on.
Questions about validate_template
validate_template is a execute tool on the FortiManager MCP Server MCP server. It is categorised as a Execute tool in the FortiManager MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the FortiManager MCP Server MCP server in PolicyLayer and add a rule for validate_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 MCP Server. Nothing to install.
validate_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_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_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_template is provided by the FortiManager MCP Server MCP server (rstierli/fortimanager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FortiManager MCP Server, and thousands of servers like it.
Across the catalogue