AI agents invoke enable_vdom to trigger actions in Fortimanager. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Based on the tool name, 'enable_vdom' likely enables a Virtual Domain (VDOM) on a FortiManager-managed device, which is an operational/configuration action that triggers external network changes. This falls under Execute as it modifies a system's operational state. However, the empty description significantly lowers confidence.
From the tool's definition Tool name: 'enable_vdom' — no description provided.
Documented attack patterns abuse exactly the kind of access enable_vdom 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 enable_vdom:
{
"version": "1",
"default": "deny",
"tools": {
"enable_vdom": {
"limits": [
{
"counter": "enable_vdom_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}enable_vdom stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
enable_vdom. It is categorised as a Execute tool in the Fortimanager MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Fortimanager MCP server in PolicyLayer and add a rule for enable_vdom: 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.
enable_vdom is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the enable_vdom 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 enable_vdom. 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.
enable_vdom 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.