retrieve_device_config
A read tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/retrieve-device-config.md
What retrieve_device_config does on Fortimanager
AI agents call retrieve_device_config 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 retrieve_device_config is rated Low
Based on the tool name alone, this is a Read operation—it retrieves device configuration from FortiManager. The empty description lowers confidence slightly, but the naming convention is consistent with other read-like tools (e.g., 'get', 'fetch'). Severity is medium because configuration data can be sensitive and could inform further attacks, but retrieval itself causes no direct harm.
From the tool's definition Tool name 'retrieve_device_config' indicates data retrieval. The verb 'retrieve' is a read operation that queries configuration data without modification.
Attacks that exploit this kind of access
The rule that runs retrieve_device_config 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 retrieve_device_config, this is the rule to start with:
retrieve_device_config 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 retrieve_device_config call is checked against it from then on.
Questions about retrieve_device_config
retrieve_device_config 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 retrieve_device_config: 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.
retrieve_device_config 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 retrieve_device_config 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 retrieve_device_config. 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.
retrieve_device_config 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