AI agents call retrieve_device_config 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.
The tool retrieves/queries configuration data from managed devices with no stated side effects. However, device configurations in a network management context (FortiManager) often contain sensitive security settings, credentials, or policy details, warranting medium severity despite being read-only. No destructive or financial impact, but unauthorized access could expose security posture and enable lateral attacks.
From the tool's definition Tool name 'retrieve_device_config' indicates data retrieval; description is empty but the verb 'retrieve' is unambiguous. Sibling tools show this server manages network device configurations (policies, templates, interfaces, zones, rules, devices).
Documented attack patterns abuse exactly the kind of access retrieve_device_config 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 retrieve_device_config:
{
"version": "1",
"default": "deny",
"tools": {
"retrieve_device_config": {}
}
}retrieve_device_config 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.
retrieve_device_config. 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.
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.