list_device_blueprints
A read tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/list-device-blueprints.md
What list_device_blueprints does on Fortimanager
AI agents call list_device_blueprints 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 list_device_blueprints is rated Low
This tool retrieves or queries device blueprint data from FortiManager. There is no indication it modifies, deletes, executes code, or creates financial obligations. The low severity reflects that listing blueprints poses minimal risk—an AI agent misusing this would only gain visibility into existing device configurations, not alter them or trigger external operations.
From the tool's definition Tool name 'list_device_blueprints' and description 'List device blueprints' indicate a retrieval operation with no side effects. The verb 'list' is a classic read-only operation that queries and returns data without modification.
Attacks that exploit this kind of access
The rule that runs list_device_blueprints 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 list_device_blueprints, this is the rule to start with:
list_device_blueprints 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 list_device_blueprints call is checked against it from then on.
Questions about list_device_blueprints
list_device_blueprints 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 list_device_blueprints: 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.
list_device_blueprints 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 list_device_blueprints 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 list_device_blueprints. 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.
list_device_blueprints 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