createTask
Create a task in a plan. Requires planId and title. Accepts every field updateTask accepts, so a task can be created complete in ONE call: no create-then-update, and no window in which other actors read a half-written record. Pass parentItemId to create it under its story, requirement or feature ...
This record as markdown: /tools/io-stablebaseline-sb/createtask.md
What createTask does on Stable Baseline
AI agents use createTask to create or update resources in Stable Baseline, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stable Baseline environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | — | Type. Default: task, which takes a TAS- id. Override only to put another kind of work item in the plan, for example a user_story (a STY- id) or a test_case (a T |
title | string | Yes | |
fields | array | — | Optional. Answer with only these fields instead of the whole task, for example ["id", "versionTimestamp"]. Any of the task's own fields (snake_case or camelCase |
planId | string | Yes | |
source | string | — | Where the work came from. Default: human_manual (shown as a general item), which is right for anything you raise yourself. Use feedback, incident, postmortem, c |
status | string | — | Initial status. Default: captured. |
phaseId | string | — | Phase to assign to. |
urgency | string | — | e.g. this_week, this_month, this_quarter. |
why_now | string | — | |
end_date | string | — | YYYY-MM-DD. |
metadata | object | — | Free-form JSON stored alongside the task. On updateTask this MERGES rather than replaces. |
owner_id | string | — | User UUID to assign as owner. MUTUALLY EXCLUSIVE with owner_team_id. Use listAssignablePrincipals(projectId, kind='user', itemKind='task') to look up valid UUID |
Parameters from the server's own tool schema.
Why createTask is rated Medium
An AI agent can call createTask faster than any human can review: one bad instruction and it creates or modifies resources in Stable Baseline by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (63 properties) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs createTask 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 createTask, this is the rule to start with:
createTask stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 createTask call is checked against it from then on.
Questions about createTask
Create a task in a plan. Requires planId and title. Accepts every field updateTask accepts, so a task can be created complete in ONE call: no create-then-update, and no window in which other actors read a half-written record. Pass parentItemId to create it under its story, requirement or feature in the work hierarchy (which may be in another plan, or in none), and linkedRecords to link database rows to it. Pass fields (for example ["id", "friendlyId", "versionTimestamp"]) for a short answer instead of the whole task. It is categorised as a Write tool in the Stable Baseline MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
createTask accepts 12 parameters: type, title, fields, planId, source, status, phaseId, urgency, why_now, end_date, metadata, owner_id. Required: title, 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 createTask: 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.
createTask is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the createTask 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 createTask. 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.
createTask 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