aos_s_show
Run 'show' commands on an AOS-S switch (all must start with 'show ', async polls ~60s).
This record as markdown: /tools/secure-ssid-centralmcp/aos-s-show.md
What aos_s_show does on API-Central
AI agents call aos_s_show 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 aos_s_show is rated Low
The tool exclusively runs 'show' commands, which are read-only diagnostic/monitoring commands on network switches. No data is modified or deleted. Medium severity because it exposes potentially sensitive network topology, configuration, and state information from infrastructure devices, and misuse could reveal security-relevant details.
From the tool's definition Run 'show' commands on an AOS-S switch (all must start with 'show ')
Attacks that exploit this kind of access
The rule that runs aos_s_show 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 aos_s_show, this is the rule to start with:
aos_s_show 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 aos_s_show call is checked against it from then on.
Questions about aos_s_show
Run 'show' commands on an AOS-S switch (all must start with 'show ', async polls ~60s). 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 aos_s_show: 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.
aos_s_show 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 aos_s_show 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 aos_s_show. 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.
aos_s_show 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