List gateway clusters for overlay/tunneled SSIDs (bounded by default).
AI agents call list_gw_clusters 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 or lists data about gateway clusters with no side effects. The word 'list' is a classic indicator of a Read category tool. The description confirms it queries gateway cluster configuration for overlay/tunneled SSIDs. There is no evidence of data creation, modification, deletion, execution, or financial operations. The 'bounded by default' qualifier suggests safe query scoping.
From the tool's definition Tool name 'list_gw_clusters' and description 'List gateway clusters' indicate a read-only query operation that retrieves information about existing gateway clusters without modification.
Attacks that exploit this kind of access
List gateway clusters for overlay/tunneled SSIDs (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_gw_clusters: 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_gw_clusters 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_gw_clusters 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_gw_clusters. 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_gw_clusters 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 →