paper_update_document

Update a Paper document title/content/status/metadata. Live writes require dryRun:false, approved:true, reason, and idempotencyKey.

SERVERStarfield SOURCE@adrata/starfield-mcp

Medium RISK CLASS

Category Write

Parameters 102 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-starfield-mcp/paper-update-document.md

WHAT IT DOES

What paper_update_document does on Starfield

AI agents use paper_update_document 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	—
`content`	string	—
`approved`	boolean	—	Must be true for live writes.
`metadata`	object	—
`idempotencyKey`	string	—	Required for live writes.
`expectedRevision`	integer	Yes

Parameters from the server's own tool schema.

RISK

Why paper_update_document is rated Medium

An AI agent can call paper_update_document 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.

Risk signalsAccepts raw HTML/template content (content) · High parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

paper_update_document Rate-limited

paper_update_document 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": {
    "paper_update_document": {
      "limits": [
        {
          "counter": "paper_update_document_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 Starfield, apply this rule, and every paper_update_document call is checked against it from then on.

FAQ

Questions about paper_update_document

What does the paper_update_document tool do? +

Update a Paper document title/content/status/metadata. 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.

What parameters does paper_update_document accept? +

paper_update_document accepts 10 parameters: id, title, dryRun, reason, status, content, approved, metadata, idempotencyKey, expectedRevision. Required: id, expectedRevision. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on paper_update_document? +

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

What risk level is paper_update_document? +

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

Can I rate-limit paper_update_document? +

Yes. Add a rate_limit block to the paper_update_document 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 paper_update_document completely? +

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

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

KEEP EXPLORING

More on Starfield, and thousands of servers like it.

This server

All 233 Starfield tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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