AI agents call get_device_system_information 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 system information from a device without creating, modifying, deleting, or executing any operations. It is a read-only query operation that has no side effects. The severity is low because disclosure of system status information, while potentially informative to an attacker, does not directly enable harmful actions on its own.
From the tool's definition Tool name 'get_device_system_information' and description 'Get detailed device system status' indicate a retrieval operation with no modification or execution of commands.
Documented attack patterns abuse exactly the kind of access get_device_system_information 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_device_system_information:
{
"version": "1",
"default": "deny",
"tools": {
"get_device_system_information": {}
}
}get_device_system_information 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 detailed device system status. 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_device_system_information: 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_device_system_information 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_device_system_information 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_device_system_information. 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_device_system_information 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.