AI agents call list_custom_applications 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.
This tool retrieves and displays existing custom application signatures from FortiManager without creating, modifying, deleting, or executing anything. It is a read-only query operation with minimal blast radius if misused by an AI agent—worst case being information disclosure of non-sensitive configuration metadata.
From the tool's definition Tool name 'list_custom_applications' and description 'List custom application signatures' indicate data retrieval with no modification, deletion, or execution.
Documented attack patterns abuse exactly the kind of access list_custom_applications 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 list_custom_applications:
{
"version": "1",
"default": "deny",
"tools": {
"list_custom_applications": {}
}
}list_custom_applications 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.
List custom application signatures. 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 list_custom_applications: 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.
list_custom_applications 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 list_custom_applications 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 list_custom_applications. 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.
list_custom_applications 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.