run_show_commands | PolicyLayer

WHAT IT DOES

What run_show_commands does on HPE Aruba Networking Central MCP Server

AI agents invoke run_show_commands to trigger actions in HPE Aruba Networking Central MCP Server. 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 IT NEEDS A POLICY

Why run_show_commands needs a policy

This tool executes network device commands ('show commands') which can trigger external operations on network infrastructure. While 'show' commands are typically read-only, the 'run' prefix indicates active command execution that could have side effects depending on arguments or actual command implementation. In a network management context, command execution is classified as Execute category.

From the tool's definition Tool name 'run_show_commands' combined with context of network management server (HPE Aruba Networking Central) that exposes REST API for network configuration and management. The 'run' verb indicates execution of commands.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_show_commands Rate-limited

run_show_commands 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_show_commands": {
      "limits": [
        {
          "counter": "run_show_commands_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches HPE Aruba Networking Central MCP Server, so you can run agents against it safely.

FAQ

Questions about run_show_commands

What does the run_show_commands tool do? +

run_show_commands. It is categorised as a Execute tool in the HPE Aruba Networking Central MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_show_commands? +

Register the HPE Aruba Networking Central MCP Server MCP server in PolicyLayer and add a rule for run_show_commands: 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 Aruba Networking Central MCP Server. Nothing to install.

What risk level is run_show_commands? +

run_show_commands is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_show_commands? +

Yes. Add a rate_limit block to the run_show_commands 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.

How do I block run_show_commands completely? +

Set action: deny in the PolicyLayer policy for run_show_commands. 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.

What MCP server provides run_show_commands? +

run_show_commands is provided by the HPE Aruba Networking Central MCP Server MCP server (the-otner/aruba-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.