terminal_execute_command
A execute tool on the Aapanel MCP server.
This record as markdown: /tools/aapanel-mcp/terminal-execute-command.md
What terminal_execute_command does on Aapanel
AI agents invoke terminal_execute_command to trigger actions in Aapanel. 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 terminal_execute_command is rated High
This tool permits execution of arbitrary shell commands on the host system, which can have unlimited side effects depending on attacker-controlled input. This is a classic Execute category risk with critical severity due to the potential for system compromise, data exfiltration, lateral movement, and complete host takeover. The empty description lowers confidence slightly, but the tool name is definitive.
From the tool's definition Tool name 'terminal_execute_command' explicitly indicates execution of arbitrary terminal/shell commands. No description provided, but the name alone is unambiguous.
Attacks that exploit this kind of access
The rule that runs terminal_execute_command safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aapanel, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For terminal_execute_command, this is the rule to start with:
terminal_execute_command 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 Aapanel, apply this rule, and every terminal_execute_command call is checked against it from then on.
Questions about terminal_execute_command
terminal_execute_command is a execute tool on the Aapanel MCP server. It is categorised as a Execute tool in the Aapanel MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aapanel MCP server in PolicyLayer and add a rule for terminal_execute_command: 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 Aapanel. Nothing to install.
terminal_execute_command 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 terminal_execute_command 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 terminal_execute_command. 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.
terminal_execute_command is provided by the Aapanel MCP server (nipunanirmal/aapanel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aapanel, and thousands of servers like it.
Across the catalogue