getTask
Get a task by ID with full details, evidence, activity, and the checklist array (each item: id, text, due_date, completed_at, plus server-stamped attribution). Returns versionTimestamp; pass it to updateTask to modify. Includes percent_complete for progress tracking.
This record as markdown: /tools/io-stablebaseline-sb/gettask.md
What getTask does on Stable Baseline
AI agents call getTask 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 |
|---|---|---|---|
taskId | string | Yes |
Parameters from the server's own tool schema.
Why getTask is rated Low
This tool retrieves and queries task data without creating, modifying, deleting, or executing operations. It is purely informational and has no side effects. The mention of versionTimestamp is a concurrency control mechanism passed to other tools, not evidence of mutation.
From the tool's definition Tool description states 'Get a task by ID with full details' and 'Returns versionTimestamp'. The primary action is retrieval of existing task data with no modification capability mentioned in the tool itself (updateTask is a separate tool).
Attacks that exploit this kind of access
The rule that runs getTask 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 getTask, this is the rule to start with:
getTask 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 getTask call is checked against it from then on.
Questions about getTask
Get a task by ID with full details, evidence, activity, and the checklist array (each item: id, text, due_date, completed_at, plus server-stamped attribution). Returns versionTimestamp; pass it to updateTask to modify. Includes percent_complete for progress tracking. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
getTask accepts 1 parameter: taskId. Required: taskId. 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 getTask: 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.
getTask 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 getTask 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 getTask. 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.
getTask 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