AI agents call task_list to retrieve information from Agent Orchestration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries task data without modifying, deleting, or executing any operations. It falls squarely into the Read category as a data retrieval function. The filtering capability is a standard query parameter and does not introduce write, execute, or destructive capabilities. Severity is low because listing existing tasks poses minimal security risk even if misused by an agent.
From the tool's definition Tool name 'task_list' and description 'List tasks with optional filters' indicate a query/retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access task_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agent Orchestration, and nothing reaches the server without passing your rules. This is the rule we recommend for task_list:
{
"version": "1",
"default": "deny",
"tools": {
"task_list": {}
}
} task_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List tasks with optional filters. It is categorised as a Read tool in the Agent Orchestration MCP Server, which means it retrieves data without modifying state.
Register the Agent Orchestration 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 Agent Orchestration. 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 Agent Orchestration MCP server (madebyaris/agent-orchestration). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Agent Orchestration, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
35 Agent Orchestration tools catalogued and risk-classified — across an index of 43,000+ MCP servers.