terminal_install_bridge
A execute tool on the Aapanel MCP server.
This record as markdown: /tools/aapanel-mcp/terminal-install-bridge.md
What terminal_install_bridge does on Aapanel
AI agents invoke terminal_install_bridge 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_install_bridge is rated High
The name implies installing a bridge for terminal access, which likely involves executing system commands or scripts to set up terminal functionality. Empty description lowers confidence, but 'install' combined with 'terminal' and 'bridge' strongly suggests execution of privileged system operations. Severity is high given potential for remote terminal access establishment.
From the tool's definition Tool name 'terminal_install_bridge' suggests installation of a terminal bridge component, implying execution of system-level operations.
Attacks that exploit this kind of access
The rule that runs terminal_install_bridge 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_install_bridge, this is the rule to start with:
terminal_install_bridge 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_install_bridge call is checked against it from then on.
Questions about terminal_install_bridge
terminal_install_bridge 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_install_bridge: 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_install_bridge 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_install_bridge 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_install_bridge. 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_install_bridge 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