change_work_item_state · MCP DevOps Plan Server MCP

WHAT IT DOES

What change_work_item_state does on MCP DevOps Plan Server

AI agents use change_work_item_state 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.

WHY IT NEEDS A POLICY

Why change_work_item_state needs a policy

This tool modifies the state of a work item, which is a reversible data change (state can be changed back). It does not delete data, execute code, or involve financial transactions. The two-step process (request + commit) suggests a controlled write operation. Severity is medium because incorrect state changes could disrupt workflow tracking across teams.

From the tool's definition Changes the state of a work item in Plan using a two-step process (movement request + commit)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

change_work_item_state Rate-limited

change_work_item_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": {
    "change_work_item_state": {
      "limits": [
        {
          "counter": "change_work_item_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 MCP DevOps Plan Server, so you can run agents against it safely.

FAQ

Questions about change_work_item_state

What does the change_work_item_state tool do? +

Changes the state of a work item in Plan using a two-step process (movement request + commit). 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.

How do I enforce a policy on change_work_item_state? +

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

What risk level is change_work_item_state? +

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

Can I rate-limit change_work_item_state? +

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

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

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