validate_template · FortiManager MCP Server MCP

WHAT IT DOES

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 IT NEEDS A POLICY

Why validate_template needs a policy

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

Recommended rule Ready

Verdict

validate_template Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "validate_template": {
      "limits": [
        {
          "counter": "validate_template_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches FortiManager MCP Server, so you can run agents against it safely.

FAQ

Questions about validate_template

What does the validate_template tool do? +

validate_template. 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.

How do I enforce a policy on validate_template? +

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.

What risk level is validate_template? +

validate_template is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit validate_template? +

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.

How do I block validate_template completely? +

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.

What MCP server provides validate_template? +

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.