Create an L2 VLAN and scope-map it (org-wide if scope_id omitted).
AI agents use create_vlan to create or update resources in API-Central — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your API-Central environment.
This tool creates a new VLAN (Virtual LAN), which is a network configuration change. VLANs can be deleted or modified later, making this a Write operation rather than Destructive. However, the severity is high because misconfigured VLANs can disrupt network segmentation, isolate critical devices, or compromise network security policies if created improperly by an agent.
From the tool's definition Tool name is 'create_vlan' and description states 'Create an L2 VLAN and scope-map it', indicating creation of network configuration that is reversible.
Attacks that exploit this kind of access
Create an L2 VLAN and scope-map it (org-wide if scope_id omitted). It is categorised as a Write tool in the API-Central MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the API-Central MCP server in PolicyLayer and add a rule for create_vlan: 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 API-Central. Nothing to install.
create_vlan 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 create_vlan 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 create_vlan. 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.
create_vlan is provided by the API-Central MCP server (secure-ssid/centralmcp). 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 →