get_system_resource_usage
Get system resource usage including CPU, memory, and disk statistics.
This record as markdown: /tools/jmpijll-fortimanager-mcp/get-system-resource-usage.md
What get_system_resource_usage does on Fortimanager
AI agents call get_system_resource_usage 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_system_resource_usage is rated Low
This tool retrieves system performance metrics and statistics without modifying any configuration, data, or state. It is a read-only diagnostic query typical of monitoring and observability tools. While exposed on a sensitive network management system (FortiManager), the information accessed is non-critical system status data rather than security-critical configurations. Misuse would have minimal blast radius.
From the tool's definition Tool name is 'get_system_resource_usage' and description explicitly states it 'Get system resource usage including CPU, memory, and disk statistics' — purely retrieval of monitoring/diagnostic data with no modification.
Attacks that exploit this kind of access
The rule that runs get_system_resource_usage 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_system_resource_usage, this is the rule to start with:
get_system_resource_usage 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_system_resource_usage call is checked against it from then on.
Questions about get_system_resource_usage
Get system resource usage including CPU, memory, and disk statistics. 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_system_resource_usage: 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_system_resource_usage 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_system_resource_usage 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_system_resource_usage. 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_system_resource_usage 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