set_vdom_meta_fields
A write tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/set-vdom-meta-fields.md
What set_vdom_meta_fields does on Fortimanager
AI agents use set_vdom_meta_fields to create or update resources in Fortimanager, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fortimanager environment.
Why set_vdom_meta_fields is rated Medium
The tool performs write operations on FortiManager VDOM metadata. While the description is empty (lowering confidence slightly), the name pattern and context among sibling tools like 'add_device_to_group', 'add_policies_to_block', and 'add_template_to_group' confirm this is part of FortiManager's configuration modification suite.
From the tool's definition Tool name 'set_vdom_meta_fields' indicates modification of VDOM (Virtual Domain) metadata fields in FortiManager. The 'set_' prefix and context within a FortiManager configuration tool suite strongly suggest data modification.
Attacks that exploit this kind of access
The rule that runs set_vdom_meta_fields 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 set_vdom_meta_fields, this is the rule to start with:
set_vdom_meta_fields stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 set_vdom_meta_fields call is checked against it from then on.
Questions about set_vdom_meta_fields
set_vdom_meta_fields is a write tool on the Fortimanager MCP server. It is categorised as a Write tool in the Fortimanager MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fortimanager MCP server in PolicyLayer and add a rule for set_vdom_meta_fields: 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.
set_vdom_meta_fields is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_vdom_meta_fields 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 set_vdom_meta_fields. 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.
set_vdom_meta_fields 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