update_workitem_state · WorkItems DevOps MCP Server MCP

WHAT IT DOES

What update_workitem_state does on WorkItems DevOps MCP Server

AI agents use update_workitem_state to create or update resources in WorkItems DevOps MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WorkItems DevOps MCP Server environment.

WHY IT NEEDS A POLICY

Why update_workitem_state needs a policy

This tool modifies work item state/status in Azure DevOps, which is a write operation that changes data but does not delete or destroy it. State changes are typically reversible (can be changed back to previous states). The empty description lowers confidence slightly, but context from the server description and sibling tools confirms the write classification.

From the tool's definition Tool name is 'update_workitem_state'; sibling tool 'update_workitem_description' is listed among Write-category operations (create, update, post, upload). The server description explicitly mentions 'status updates' as a supported capability.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_workitem_state Rate-limited

update_workitem_state 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": {
    "update_workitem_state": {
      "limits": [
        {
          "counter": "update_workitem_state_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches WorkItems DevOps MCP Server, so you can run agents against it safely.

FAQ

Questions about update_workitem_state

What does the update_workitem_state tool do? +

update_workitem_state. It is categorised as a Write tool in the WorkItems DevOps MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_workitem_state? +

Register the WorkItems DevOps MCP Server MCP server in PolicyLayer and add a rule for update_workitem_state: 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 WorkItems DevOps MCP Server. Nothing to install.

What risk level is update_workitem_state? +

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

Can I rate-limit update_workitem_state? +

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

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

update_workitem_state is provided by the WorkItems DevOps MCP Server MCP server (juanpq26/workitems_devops_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.