flag_work_item

SERVERStarfield SOURCE@adrata/starfield-mcp

Critical RISK CLASS

Category Destructive

Parameters 63 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What flag_work_item does on Starfield

AI agents call flag_work_item to permanently remove resources in Starfield, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Parameter	Type	Required	Description
`dryRun`	boolean	—	Defaults to true. Set false to change the flag.
`itemId`	string	Yes	Card id.
`reason`	string	Yes	REQUIRED. Raising: what is wrong with the card. Clearing: what resolved it. Shown on the card and appended to its comment thread — write it for the person who w
`flagged`	boolean	Yes	true raises the flag; false clears it. Raising an already-flagged card replaces the reason.
`approved`	boolean	—	Required true for a live change.
`idempotencyKey`	string	—	Required for a live change. Reuse the SAME key on retry — the flag also appends a comment.

Parameters from the server's own tool schema.

RISK

Why flag_work_item is rated Critical

An AI agent that decides to call flag_work_item doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Starfield is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

flag_work_item Hidden

flag_work_item is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "flag_work_item"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about flag_work_item

What does the flag_work_item tool do? +

Flag a card as having a problem WITH THE CARD — unclear scope, no repro, a blocked dependency, a question waiting on an answer — or clear a flag once it is resolved. A flagged card is drawn differently on the board so nobody picks it up by mistake. A FLAG IS NOT A TAG. The tag says how urgent the WORK is; a flag says the CARD is not fit to be worked. If a card is merely important, use set_work_item_tag. If you cannot start because something is missing, flag it. THE REASON IS REQUIRED IN BOTH DIRECTIONS, and it is not the audit reason — it is the text a human reads on the card. Raising says what is wrong; clearing says what resolved it. Anyone may clear a flag, which only works because both directions are recorded as a comment on the card. This is what the ship-the-card skill means by "an unworkable card is a triage problem, not a coding problem": flag it, say the one question that would unblock it, and stop. 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 Destructive tool in the Starfield MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does flag_work_item accept? +

flag_work_item accepts 6 parameters: dryRun, itemId, reason, flagged, approved, idempotencyKey. Required: itemId, reason, flagged. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on flag_work_item? +

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

flag_work_item is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit flag_work_item? +

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

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

flag_work_item 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 → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →