tasks_list
List your tasks, or another agent's tasks (read-only) using from_agent_id. Use filters to narrow results.
This record as markdown: /tools/io-github-saloprj-dialogbrain/tasks-list.md
What tasks_list does on Dialogbrain
AI agents call tasks_list to retrieve information from Dialogbrain without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Max results (default 20) |
status | string | — | |
overdue | boolean | — | If true, only return tasks past due_at that are not done |
agent_id | integer | — | Agent ID whose tasks to list. Required when calling from MCP. |
thread_id | integer | — | Filter by related thread |
from_agent_id | integer | — | List tasks of another agent (read-only). Omit to list your own. |
assigned_to_contact_id | integer | — | Filter by assigned contact |
Parameters from the server's own tool schema.
Why tasks_list is rated Low
This tool retrieves and queries task data without side effects. The 'read-only' designation and use of filters to narrow results confirm it is a data retrieval operation with no capacity to modify, create, or delete tasks. It poses minimal security risk as it only enables information access.
From the tool's definition Tool name 'tasks_list' and description explicitly states 'read-only' for listing tasks with optional filtering. No modification, deletion, or execution capabilities mentioned.
Attacks that exploit this kind of access
The rule that runs tasks_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tasks_list, this is the rule to start with:
tasks_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 Dialogbrain, apply this rule, and every tasks_list call is checked against it from then on.
Questions about tasks_list
List your tasks, or another agent's tasks (read-only) using from_agent_id. Use filters to narrow results. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
tasks_list accepts 7 parameters: limit, status, overdue, agent_id, thread_id, from_agent_id, assigned_to_contact_id. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for tasks_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 Dialogbrain. Nothing to install.
tasks_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 tasks_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 tasks_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.
tasks_list is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
This server
Across the catalogue