get_switch_stacking_info
A read tool on the API-Central MCP server.
This record as markdown: /tools/secure-ssid-centralmcp/get-switch-stacking-info.md
What get_switch_stacking_info does on API-Central
AI agents call get_switch_stacking_info to retrieve information from API-Central without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_switch_stacking_info is rated Low
The 'get_' prefix strongly signals a read operation that retrieves or queries existing data about switch stacking configuration without modifying state. While the description is empty (lowering confidence), the naming pattern and position within a monitoring/configuration automation platform for HPE Aruba Central indicates this is a query tool.
From the tool's definition Tool name 'get_switch_stacking_info' indicates a retrieval operation (prefix 'get_') that queries switch stacking information. Description is empty, but the name and context within a network operations monitoring suite suggests read-only functionality.
Attacks that exploit this kind of access
The rule that runs get_switch_stacking_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_switch_stacking_info, this is the rule to start with:
get_switch_stacking_info 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 API-Central, apply this rule, and every get_switch_stacking_info call is checked against it from then on.
Questions about get_switch_stacking_info
get_switch_stacking_info is a read tool on the API-Central MCP server. 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_stacking_info: 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_stacking_info 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_stacking_info 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_stacking_info. 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_stacking_info 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.
More on API-Central, and thousands of servers like it.
This server
Across the catalogue