listTasks
List AND grep tasks in a plan. query searches the title, friendlyId and description, not just the title (substring by default; set isRegex:true for a regular expression, caseSensitive:true for exact case). Supports filtering by status, priority, phaseId and parentItemId (a story's tasks in the wo...
This record as markdown: /tools/io-stablebaseline-sb/listtasks.md
What listTasks does on Stable Baseline
AI agents call listTasks to retrieve information from Stable Baseline 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 | number | — | Max results (1-100, default 50). |
query | string | — | Grep across title, friendlyId and description. Substring by default; a regular expression when isRegex:true; case-insensitive unless caseSensitive:true. |
offset | number | — | Pagination offset. |
planId | string | Yes | |
status | string | — | Filter by status. |
isRegex | boolean | — | Treat query as a regular expression (grep -E), e.g. "ACME-\d+". Default false (literal substring). |
phaseId | string | — | Filter by phase. |
priority | string | — | Filter by priority. |
sortField | string | — | Sort field. Default: position. |
parentItemId | string | — | Only the children of this item in the work hierarchy (its UUID or friendly id, such as IMP-12), whatever plan or phase they are in. "none" lists only the items |
caseSensitive | boolean | — | Case-sensitive matching. Default false. |
sortAscending | boolean | — | Sort ascending. Default: true. |
Parameters from the server's own tool schema.
Why listTasks is rated Low
Even though listTasks only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (15 properties) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs listTasks safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For listTasks, this is the rule to start with:
listTasks 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 Stable Baseline, apply this rule, and every listTasks call is checked against it from then on.
Questions about listTasks
List AND grep tasks in a plan. query searches the title, friendlyId and description, not just the title (substring by default; set isRegex:true for a regular expression, caseSensitive:true for exact case). Supports filtering by status, priority, phaseId and parentItemId (a story's tasks in the work hierarchy, say). Every task carries its versionTimestamp, ready for updateTask, so one call here supplies the tokens for a whole batch of updates, its parent_item_id and parentItem (the item it belongs to in the work hierarchy, or null), and linkedRecords, the database rows it links (as getTask describes them); filter by them with hasLinkedRecords, linkedRecordIds and linkedTableIds. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
listTasks accepts 12 parameters: limit, query, offset, planId, status, isRegex, phaseId, priority, sortField, parentItemId, caseSensitive, sortAscending. Required: planId. The full parameter table on this page comes from the server's own tool schema.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for listTasks: 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 Stable Baseline. Nothing to install.
listTasks 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 listTasks 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 listTasks. 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.
listTasks is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stable Baseline, and thousands of servers like it.
This server
Across the catalogue