List VLANs active on a switch (status, membership). filter: OData e.g. "status in ('Up')".
AI agents call get_switch_vlans to retrieve information from API-Central without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries network configuration data (VLAN status and membership information) with no side effects. It performs data retrieval only, matching the 'Read' category definition. The low severity reflects that unauthorized VLAN enumeration presents minimal immediate risk compared to configuration changes or network disruption.
From the tool's definition Tool name 'get_switch_vlans' and description 'List VLANs active on a switch' indicate a read-only query operation. The description explicitly references filtering via OData, which is a query standard for retrieving data without modification.
Attacks that exploit this kind of access
List VLANs active on a switch (status, membership). filter: OData e.g. "status in ('Up')". It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.
Register the API-Central MCP server in PolicyLayer and add a rule for get_switch_vlans: 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.
get_switch_vlans is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_switch_vlans 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 get_switch_vlans. 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.
get_switch_vlans 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 →