ap_show
Run 'show' commands on an AP (all must start with 'show ', max 20, async polls ~60s).
This record as markdown: /tools/hpe-networking-mcp/ap-show.md
What ap_show does on Hpe Networking
AI agents invoke ap_show to trigger actions in Hpe Networking. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why ap_show is rated High
Although 'show' commands are read-only by nature, this tool actively executes CLI commands on network infrastructure (APs) and involves async polling. It triggers external operations on live devices rather than simply querying an API, placing it in the Execute category. Severity is medium because misuse could expose sensitive network configuration data or cause load on devices, but no direct data modification occurs.
From the tool's definition Run 'show' commands on an AP (all must start with 'show ', max 20, async polls ~60s)
Attacks that exploit this kind of access
The rule that runs ap_show safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hpe Networking, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ap_show, this is the rule to start with:
ap_show stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hpe Networking, apply this rule, and every ap_show call is checked against it from then on.
Questions about ap_show
Run 'show' commands on an AP (all must start with 'show ', max 20, async polls ~60s). It is categorised as a Execute tool in the Hpe Networking MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Hpe Networking MCP server in PolicyLayer and add a rule for ap_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 Hpe Networking. Nothing to install.
ap_show is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ap_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 ap_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.
ap_show is provided by the Hpe Networking MCP server (secure-ssid/hpe-networking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hpe Networking, and thousands of servers like it.
Across the catalogue