AI agents call get_fmg_uptime 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 queries FortiManager for read-only system uptime and boot time metrics. It does not create, modify, delete, or execute operations—it merely retrieves and returns existing system information. This is a straightforward Read operation with low severity, as disclosure of uptime data poses minimal risk to system security or operations.
From the tool's definition Tool name 'get_fmg_uptime' and description 'Get FortiManager system uptime and boot time' indicate a query operation that retrieves system status information with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_fmg_uptime 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_fmg_uptime:
{
"version": "1",
"default": "deny",
"tools": {
"get_fmg_uptime": {}
}
}get_fmg_uptime 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 FortiManager system uptime and boot time. 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_fmg_uptime: 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_fmg_uptime 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_fmg_uptime 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_fmg_uptime. 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_fmg_uptime 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.