List all tasks, optionally filtered by status.
AI agents call list-tasks to retrieve information from Back-Agent MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing task data with optional filtering. It has no side effects—it neither creates, modifies, deletes, nor executes tasks. The query nature and read-only semantics place it firmly in the Read category. Severity is low because listing tasks poses minimal risk; the worst outcome is information disclosure of task metadata, which is not sensitive by default in a development context.
From the tool's definition Tool name 'list-tasks' and description 'List all tasks, optionally filtered by status' indicate a query operation that retrieves task information without modifying, deleting, or executing anything.
Attacks that exploit this kind of access
List all tasks, optionally filtered by status. It is categorised as a Read tool in the Back-Agent MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Back-Agent MCP Server MCP server in PolicyLayer and add a rule for list-tasks: 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 Back-Agent MCP Server. Nothing to install.
list-tasks 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 list-tasks 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 list-tasks. 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.
list-tasks is provided by the Back-Agent MCP Server MCP server (zuens2020/back-agent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →