get_security_profile_entry_count
A read tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/get-security-profile-entry-count.md
What get_security_profile_entry_count does on Fortimanager
AI agents call get_security_profile_entry_count to retrieve information from Fortimanager without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_security_profile_entry_count is rated Low
The 'get' prefix is a standard indicator of read-only operations. Counting entries is a non-destructive query with no side effects. While the empty description reduces confidence slightly, the tool name's structure and its position among other FortiManager tools (which include write/execute operations like 'add_*' and 'abort_*') confirms this as a passive information retrieval tool.
From the tool's definition Tool name 'get_security_profile_entry_count' contains 'get' verb, indicating a retrieval operation. No description provided, but the naming convention and context within a FortiManager configuration server strongly suggest a query that counts entries in a…
Attacks that exploit this kind of access
The rule that runs get_security_profile_entry_count safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fortimanager, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_security_profile_entry_count, this is the rule to start with:
get_security_profile_entry_count is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Fortimanager, apply this rule, and every get_security_profile_entry_count call is checked against it from then on.
Questions about get_security_profile_entry_count
get_security_profile_entry_count is a read tool on the Fortimanager MCP server. 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_security_profile_entry_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_security_profile_entry_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_security_profile_entry_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_security_profile_entry_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_security_profile_entry_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.
More on Fortimanager, and thousands of servers like it.
This server
Across the catalogue