Updates fields of an existing work item. Provide the fields you want to update with their new values. IMPORTANT: When assigning a Sprint to a work item, the work item MUST first have the corresponding Release assigned to its PlannedRelease field. You cannot assign a sprint to a work item unless t...
AI agents use update_work_item to create or update resources in MCP DevOps Plan Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP DevOps Plan Server environment.
The tool modifies existing work item data (fields) rather than reading, executing arbitrary commands, deleting, or moving money. Updates are typically reversible by applying subsequent updates with different values. While it operates on project management data, the blast radius is moderate—incorrect updates could cause workflow disruption or lost productivity, but changes can be corrected.
From the tool's definition Tool description states it 'Updates fields of an existing work item' with new values. This is a reversible modification operation that changes data without deletion.
Attacks that exploit this kind of access
Updates fields of an existing work item. Provide the fields you want to update with their new values. IMPORTANT: When assigning a Sprint to a work item, the work item MUST first have the corresponding Release assigned to its PlannedRelease field. You cannot assign a sprint to a work item unless that work item is already part of the release that owns the sprint. Always update PlannedRelease before updating Sprint field. It is categorised as a Write tool in the MCP DevOps Plan Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP DevOps Plan Server MCP server in PolicyLayer and add a rule for update_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 MCP DevOps Plan Server. Nothing to install.
update_work_item 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 update_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.
Set action: deny in the PolicyLayer policy for update_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.
update_work_item is provided by the MCP DevOps Plan Server MCP server (mrchris2000/mcp-devops-plan). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →