List overlay (tunneled/GRE) WLAN profiles (bounded by default).
AI agents call list_overlay_wlans 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 displays existing WLAN profile configurations without creating, modifying, deleting, or executing any network operations. It is bounded by default, limiting scope. The blast radius of misuse is minimal—an attacker would only gain visibility into existing WLAN configurations, not the ability to modify network behavior or access sensitive operations.
From the tool's definition Tool name 'list_overlay_wlans' with description 'List overlay (tunneled/GRE) WLAN profiles' indicates a query/retrieval operation with no modification or execution of commands. The verb 'list' is a classic Read operation.
Attacks that exploit this kind of access
List overlay (tunneled/GRE) WLAN profiles (bounded by default). 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_overlay_wlans: 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_overlay_wlans 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_overlay_wlans 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_overlay_wlans. 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_overlay_wlans 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 →