Get hit count statistics showing which policies are actively used.
AI agents call get_policy_hit_count 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 usage statistics about existing policies. It performs no write, delete, execute, or financial operations. The data returned is observational (hit counts) and does not modify any system state or trigger external actions. This is a standard read operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name is 'get_policy_hit_count' and description states 'Get hit count statistics showing which policies are actively used' — the verb 'get' combined with 'statistics' and 'showing' indicate a read-only query operation that retrieves data without…
Documented attack patterns abuse exactly the kind of access get_policy_hit_count 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 get_policy_hit_count:
{
"version": "1",
"default": "deny",
"tools": {
"get_policy_hit_count": {}
}
}get_policy_hit_count 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.
Get hit count statistics showing which policies are actively used. 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 get_policy_hit_count: 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.
get_policy_hit_count 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 get_policy_hit_count 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 get_policy_hit_count. 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.
get_policy_hit_count 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.