terminal_list_servers

A read tool on the Aapanel MCP server.

SERVERAapanel SOURCEnipunanirmal/aapanel-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aapanel-mcp/terminal-list-servers.md

WHAT IT DOES

What terminal_list_servers does on Aapanel

AI agents call terminal_list_servers to retrieve information from Aapanel without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why terminal_list_servers is rated Low

The 'list' verb pattern strongly suggests this tool retrieves or queries existing server data without modifying state. Given the naming convention among sibling tools (abnormal_check_*, alert_*) which are also informational, this appears to be a Read operation. The empty description prevents higher confidence, but the semantic meaning of 'list' in API/tool naming conventions points clearly to data retrieval.

From the tool's definition Tool name 'terminal_list_servers' contains 'list', which indicates data retrieval without side effects. The empty description limits confidence but the naming pattern suggests querying server information.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs terminal_list_servers 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_list_servers, this is the rule to start with:

terminal_list_servers Allowed

terminal_list_servers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "terminal_list_servers": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aapanel, apply this rule, and every terminal_list_servers call is checked against it from then on.

FAQ

Questions about terminal_list_servers

What does the terminal_list_servers tool do? +

terminal_list_servers is a read tool on the Aapanel MCP server. It is categorised as a Read tool in the Aapanel MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on terminal_list_servers? +

Register the Aapanel MCP server in PolicyLayer and add a rule for terminal_list_servers: 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.

What risk level is terminal_list_servers? +

terminal_list_servers is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit terminal_list_servers? +

Yes. Add a rate_limit block to the terminal_list_servers 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 terminal_list_servers completely? +

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

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

KEEP EXPLORING

More on Aapanel, and thousands of servers like it.

This server

All 282 Aapanel tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →