set_work_item_tag

SERVERStarfield SOURCE@adrata/starfield-mcp

Medium RISK CLASS

Category Write

Parameters 94 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-starfield-mcp/set-work-item-tag.md

WHAT IT DOES

What set_work_item_tag does on Starfield

AI agents use set_work_item_tag 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
`dryRun`	boolean	—	Defaults to true. Set false for a live change.
`itemId`	string	Yes	Card id.
`reason`	string	—	Required for a live change: why this tag.
`source`	string	Yes	Who decided. An agent classifying a card is "model" — claiming "human" would launder a guess as a person's judgement.
`approved`	boolean	—	Required true for a live change.
`optionId`	string	Yes	Option within the scheme — e.g. critical \| non-critical, p0..p3, all-customers \| some-customers \| internal-only.
`schemeId`	string	Yes	Urgency vocabulary. Use the board's own tagScheme unless deliberately changing it. "kind" is no longer a scheme — it is a field, set with set_work_item_kind.
`confidence`	number	—	0-1. REQUIRED when source is "model".
`idempotencyKey`	string	—	Required for a live change.

Parameters from the server's own tool schema.

RISK

Why set_work_item_tag is rated Medium

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

RECOMMENDED RULE

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

set_work_item_tag Rate-limited

set_work_item_tag 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": {
    "set_work_item_tag": {
      "limits": [
        {
          "counter": "set_work_item_tag_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 set_work_item_tag call is checked against it from then on.

FAQ

Questions about set_work_item_tag

What does the set_work_item_tag tool do? +

Set a card's URGENCY tag. The scheme must be one the board reads (severity | priority | impact) and the source must be human, model, or rules. A "model" tag REQUIRES a confidence: the board drops a low-confidence model tag, and a model tag with no confidence cannot be held to that floor, so it would be trusted by default — backwards. This does NOT say what kind of work the card is — that is a separate field; use set_work_item_kind, and note that setting one never disturbs the other. Governed write: previews by default. A live write requires dryRun:false plus approved:true, a reason, and an idempotencyKey (reuse the SAME key on retry — a duplicate move would read as the card having bounced between columns). 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 set_work_item_tag accept? +

set_work_item_tag accepts 9 parameters: dryRun, itemId, reason, source, approved, optionId, schemeId, confidence, idempotencyKey. Required: itemId, source, optionId, schemeId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on set_work_item_tag? +

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

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

Can I rate-limit set_work_item_tag? +

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

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

set_work_item_tag 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

emit_assumption_set on 0sec →add-tag on Kanban MCP Server →kb_tag on Persistent Kb →team_manager_set_sources on Team Manager MCP → The MCP Attack Database →

Guides

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