listPlans
List AND grep plans in a project. 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 and priority. projectId is required unless changedSince is ...
This record as markdown: /tools/io-stablebaseline-sb/listplans.md
What listPlans does on Stable Baseline
AI agents call listPlans 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. |
fields | array | — | Field projection. Valid fields: id, friendly_id, friendlyId, title, description, status, priority, icon, color, start_date, startDate, end_date, endDate, create |
offset | number | — | Pagination offset. |
status | string | — | Filter: draft, planning, active, on_hold, completed, cancelled. |
isRegex | boolean | — | Treat query as a regular expression (grep -E), e.g. "ACME-\d+". Default false (literal substring). |
priority | string | — | Filter: low, medium, high, critical. |
timeZone | string | — | The IANA time zone the window and its times are in, such as Australia/Sydney. Default: the person's own (the zone their browser last saved), else UTC. |
projectId | string | — | |
sortField | string | — | Sort field. Default: created_at. |
workspaceId | string | — | With changedSince and no projectId: only what changed in this workspace. Neither: your whole organisation. |
changedSince | string | — | What changed: only what was added or edited from this point, newest change first, each with who changed it and when. A period: today, yesterday, this_week, last |
Parameters from the server's own tool schema.
Why listPlans is rated Low
Even though listPlans 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)
Attacks that exploit this kind of access
The rule that runs listPlans 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 listPlans, this is the rule to start with:
listPlans 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 listPlans call is checked against it from then on.
Questions about listPlans
List AND grep plans in a project. 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 and priority. projectId is required unless changedSince is given. WHAT CHANGED: give changedSince (a period such as this_week, or a date) to list only the plans added or changed in that time, newest change first, each with change: what happened, when (in words, in the person's time zone), by whom (a person's name, and the agent's key when one did it), and what happened to each in that time in words (status and field changes, comments). With no project named it covers a workspace (workspaceId) or your whole organisation. Only what the caller may open is listed. A plan's tasks are work items: listImprovements with the same changedSince lists them. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
listPlans accepts 12 parameters: limit, query, fields, offset, status, isRegex, priority, timeZone, projectId, sortField, workspaceId, changedSince. 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 listPlans: 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.
listPlans 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 listPlans 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 listPlans. 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.
listPlans 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