AI agents call list_url_filters 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 queries URL filter objects from FortiManager without side effects. It is a read-only operation that simply enumerates existing filter configurations. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an attacker would only gain visibility into existing URL filter configurations.
From the tool's definition Tool name contains 'list' and description states 'List URL filter objects' - a retrieval operation with no modification, deletion, or execution of code.
Documented attack patterns abuse exactly the kind of access list_url_filters 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_url_filters:
{
"version": "1",
"default": "deny",
"tools": {
"list_url_filters": {}
}
}list_url_filters 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 URL filter objects. 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_url_filters: 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_url_filters 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_url_filters 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_url_filters. 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_url_filters 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.