create_vlan_interface · API-Central MCP: Risk & Policy

WHAT IT DOES

What create_vlan_interface does on API-Central

AI agents use create_vlan_interface 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.

WHY IT NEEDS A POLICY

Why create_vlan_interface needs a policy

This tool creates a new Layer 3 VLAN interface on network devices. While the action is reversible (SVIs can be deleted), it modifies critical network infrastructure configuration. The high severity reflects the potential for network disruption if misconfigured—an AI agent creating unintended VLANs could cause connectivity issues, segmentation problems, or operational outages.

From the tool's definition Tool name 'create_vlan_interface' and description 'Create an L3 SVI at device scope' explicitly indicates creation of network configuration. SVI (Switched Virtual Interface) creation is a reversible write operation that modifies device network settings.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_vlan_interface Rate-limited

create_vlan_interface 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_vlan_interface": {
      "limits": [
        {
          "counter": "create_vlan_interface_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches API-Central, so you can run agents against it safely.

FAQ

Questions about create_vlan_interface

What does the create_vlan_interface tool do? +

Create an L3 SVI at device scope (global L2 VLAN shell is auto-confirmed). 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.

How do I enforce a policy on create_vlan_interface? +

Register the API-Central MCP server in PolicyLayer and add a rule for create_vlan_interface: 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.

What risk level is create_vlan_interface? +

create_vlan_interface is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_vlan_interface? +

Yes. Add a rate_limit block to the create_vlan_interface 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 create_vlan_interface completely? +

Set action: deny in the PolicyLayer policy for create_vlan_interface. 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 create_vlan_interface? +

create_vlan_interface 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.