This record as markdown: /tools/aapanel-mcp/task-list.md
What task_list does on Aapanel
AI agents call task_list 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.
Why task_list is rated Low
This tool queries and retrieves information about background tasks without modifying, executing, or deleting anything. It has no capacity to change system state. The blast radius of misuse is minimal—an attacker gains visibility into running tasks but cannot directly impact system integrity or confidentiality beyond information disclosure.
From the tool's definition Tool name 'task_list' and description 'List background tasks' indicate a retrieval operation with no side effects. The verb 'List' is characteristic of Read operations.
Attacks that exploit this kind of access
The rule that runs task_list 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 task_list, this is the rule to start with:
task_list is read-only, so it stays allowed. 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 task_list call is checked against it from then on.
Questions about task_list
List background tasks. It is categorised as a Read tool in the Aapanel MCP Server, which means it retrieves data without modifying state.
Register the Aapanel MCP server in PolicyLayer and add a rule for task_list: 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.
task_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the task_list 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 task_list. 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.
task_list 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.
This server
Across the catalogue