list_device_vdoms
AI agents call list_device_vdoms to retrieve information from FortiManager MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates VDOMs from managed devices without modifying any configuration, data, or state. It has no side effects and represents a straightforward read-only query operation. Blast radius is minimal—unauthorized access could expose network topology information but cannot modify policies, devices, or financial transactions.
From the tool's definition Tool name 'list_device_vdoms' explicitly uses the 'list' verb, which is a retrieval operation. Given the context of a FortiManager API for centralized management, this tool queries virtual domain (VDOM) information on managed devices.
Attacks that exploit this kind of access
list_device_vdoms. It is categorised as a Read tool in the FortiManager MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FortiManager MCP Server MCP server in PolicyLayer and add a rule for list_device_vdoms: 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 MCP Server. Nothing to install.
list_device_vdoms 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_vdoms 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_vdoms. 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_vdoms is provided by the FortiManager MCP Server MCP server (rstierli/fortimanager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →