This record as markdown: /tools/takashito-linode-mcp-server/list-vlans.md
What list_vlans does on Linode MCP Server
AI agents call list_vlans to retrieve information from Linode MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_vlans is rated Low
This tool retrieves information about Virtual Local Area Networks (VLANs) in the Linode environment. Listing operations are read-only with no side effects, no code execution, and no data modification. The blast radius of misuse is minimal—an attacker could enumerate network topology but cannot modify, delete, or execute actions. This is a standard Read category tool.
From the tool's definition Tool name is 'list_vlans' and description states 'List all VLANs' - a query operation that retrieves network configuration data without modification or execution.
Attacks that exploit this kind of access
The rule that runs list_vlans safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Linode MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_vlans, this is the rule to start with:
list_vlans is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Linode MCP Server, apply this rule, and every list_vlans call is checked against it from then on.
Questions about list_vlans
List all VLANs. It is categorised as a Read tool in the Linode MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Linode MCP Server MCP server in PolicyLayer and add a rule for list_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 Linode MCP Server. Nothing to install.
list_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_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_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_vlans is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Linode MCP Server, and thousands of servers like it.
This server
Across the catalogue