paper_update_task
Update a Paper task/action title or status. Live writes require dryRun:false, approved:true, reason, and idempotencyKey.
This record as markdown: /tools/adrata-starfield-mcp/paper-update-task.md
What paper_update_task does on Starfield
AI agents use paper_update_task to create or update resources in Starfield, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Starfield environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | |
title | string | — | |
dryRun | boolean | — | Defaults to true. Set false only after explicit user approval. |
reason | string | — | Audit reason for live writes. |
status | string | — | |
approved | boolean | — | Must be true for live writes. |
idempotencyKey | string | — | Required for live writes. |
Parameters from the server's own tool schema.
Why paper_update_task is rated Medium
An AI agent can call paper_update_task faster than any human can review: one bad instruction and it creates or modifies resources in Starfield by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs paper_update_task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Starfield, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For paper_update_task, this is the rule to start with:
paper_update_task 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 Starfield, apply this rule, and every paper_update_task call is checked against it from then on.
Questions about paper_update_task
Update a Paper task/action title or status. Live writes require dryRun:false, approved:true, reason, and idempotencyKey. It is categorised as a Write tool in the Starfield MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
paper_update_task accepts 7 parameters: id, title, dryRun, reason, status, approved, idempotencyKey. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Starfield MCP server in PolicyLayer and add a rule for paper_update_task: 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 Starfield. Nothing to install.
paper_update_task 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 paper_update_task 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 paper_update_task. 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.
paper_update_task is provided by the Starfield MCP server (@adrata/starfield-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Starfield, and thousands of servers like it.
This server
Across the catalogue