updateTask

SERVERStable Baseline SOURCEhttps://api.stablebaseline.io/functions/v1/cloud-serve/mcp

Medium RISK CLASS

Category Write

Parameters 121 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-stablebaseline-sb/updatetask.md

WHAT IT DOES

What updateTask does on Stable Baseline

AI agents use updateTask 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	—
`title`	string	—
`status`	string	—
`taskId`	string	Yes
`plan_id`	string	—	Link to plan. Null to unlink.
`urgency`	string	—
`why_now`	string	—
`end_date`	string	—	YYYY-MM-DD.
`metadata`	object	—
`owner_id`	string \| null	—	User UUID to assign as owner, or null to unassign. MUTUALLY EXCLUSIVE with owner_team_id — when switching from a user to a team owner, send `owner_id: null` in
`phase_id`	string	—	Assign to phase. Null to unassign.
`position`	number	—

Parameters from the server's own tool schema.

RISK

Why updateTask is rated Medium

This tool creates or modifies data reversibly without deleting or destroying it. Status transitions, date changes, and ownership updates can all be reverted or corrected. The optimistic locking mechanism suggests a collaborative environment where conflicts are managed rather than destructive overwrites occurring.

From the tool's definition Tool description states 'Update a task' and supports reversible modifications including 'status transitions', 'dates', 'owner', 'percent_complete', 'checklist', 'acceptance_criteria'.

Risk signalsHigh parameter count (54 properties) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs updateTask 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 updateTask, this is the rule to start with:

updateTask Rate-limited

updateTask 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "updateTask": {
      "limits": [
        {
          "counter": "updatetask_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every updateTask call is checked against it from then on.

FAQ

Questions about updateTask

What does the updateTask tool do? +

Update a task. Tasks share a row with improvements (improvement_items with is_task=true), so this is a thin alias over updateImprovement — every field on updateImprovement is supported, including checklist, acceptance_criteria, status transitions (blocked/rejected/done need their respective comments), dates, owner, percent_complete, etc. Requires versionTimestamp from getTask for optimistic locking. To edit checklist items: call getTask, modify the checklist array (preserving each row's id to keep its attribution stamps), and pass the full array back here — array order is the sort order. Assignment: pass owner_id=<uuid> to assign to a user, owner_team_id=<uuid> to assign to a team (mutually exclusive — the DB enforces with a CHECK constraint). To unassign, pass owner_id=null AND owner_team_id=null. To switch owner kind, send the new value AND null the old one in the SAME call. 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.

What parameters does updateTask accept? +

updateTask accepts 12 parameters: type, title, status, taskId, plan_id, urgency, why_now, end_date, metadata, owner_id, phase_id, position. Required: taskId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on updateTask? +

Register the Stable Baseline MCP server in PolicyLayer and add a rule for updateTask: 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.

What risk level is updateTask? +

updateTask is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit updateTask? +

Yes. Add a rate_limit block to the updateTask 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.

How do I block updateTask completely? +

Set action: deny in the PolicyLayer policy for updateTask. 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.

What MCP server provides updateTask? +

updateTask 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.

KEEP EXPLORING

More on Stable Baseline, and thousands of servers like it.

This server

All 196 Stable Baseline tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →