enable_vdom

A execute tool on the Fortimanager MCP server.

SERVERFortimanager SOURCEjmpijll/fortimanager-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/jmpijll-fortimanager-mcp/enable-vdom.md

WHAT IT DOES

What enable_vdom does on Fortimanager

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.

RISK

Why enable_vdom is rated High

Based on the name alone, 'enable_vdom' likely triggers a configuration change that activates a VDOM (Virtual Domain) on a network device. This would constitute a Write or Execute operation.

From the tool's definition Tool name 'enable_vdom' suggests enabling a Virtual Domain (VDOM) on a FortiManager-managed device, but the description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs enable_vdom 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 enable_vdom, this is the rule to start with:

enable_vdom Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "enable_vdom": {
      "limits": [
        {
          "counter": "enable_vdom_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Fortimanager, apply this rule, and every enable_vdom call is checked against it from then on.

FAQ

Questions about enable_vdom

What does the enable_vdom tool do? +

enable_vdom is a execute tool on the Fortimanager MCP server. 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.

How do I enforce a policy on enable_vdom? +

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.

What risk level is enable_vdom? +

enable_vdom is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit enable_vdom? +

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.

How do I block enable_vdom completely? +

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.

What MCP server provides enable_vdom? +

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.

KEEP EXPLORING

More on Fortimanager, and thousands of servers like it.

This server

All 584 Fortimanager tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →