List named VLANs configured at the group/scope level in Central.
AI agents call list_named_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 VLAN configuration information from the Aruba Central network management platform. It performs a simple query/fetch operation with no side effects, no data modification, and no execution of commands. The blast radius of misuse is minimal—an agent could only view existing VLAN configurations, not alter network topology or cause operational impact.
From the tool's definition Tool name is 'list_named_vlans' and description states 'List named VLANs configured at the group/scope level in Central.' The verb 'list' is a read operation that retrieves and queries configuration data without modifying or deleting anything.
Attacks that exploit this kind of access
List named VLANs configured at the group/scope level in Central. 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 list_named_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.
list_named_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 list_named_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 list_named_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.
list_named_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 →