AI agents call export_templates to retrieve information from Fortimanager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'export_templates' suggests a read/retrieval operation (exporting data out), which would classify as Read. However, the empty description significantly lowers confidence. In the context of FortiManager, templates are configuration objects, and exporting them is typically a non-destructive read operation. Severity is medium given the sensitivity of network configuration data that could be exposed.
From the tool's definition Tool name: export_templates; description is empty/uninformative.
Documented attack patterns abuse exactly the kind of access export_templates 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 export_templates:
{
"version": "1",
"default": "deny",
"tools": {
"export_templates": {}
}
}export_templates is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
export_templates. It is categorised as a Read tool in the Fortimanager MCP Server, which means it retrieves data without modifying state.
Register the Fortimanager MCP server in PolicyLayer and add a rule for export_templates: 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.
export_templates is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the export_templates 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 export_templates. 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.
export_templates 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.