move_to_iteration · Azure DevOps MCP Server MCP

WHAT IT DOES

What move_to_iteration does on Azure DevOps MCP Server

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

WHY IT NEEDS A POLICY

Why move_to_iteration needs a policy

This tool modifies existing data (a work item's iteration field) in a reversible manner. The change can be undone by moving the item back to its original iteration. It does not create new data (Write, not Create), does not execute arbitrary code, and does not permanently delete or destroy data.

From the tool's definition Tool name 'move_to_iteration' and description 'Move a work item to a different iteration/sprint' indicate modification of work item state by changing its iteration assignment.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_to_iteration Rate-limited

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

FAQ

Questions about move_to_iteration

What does the move_to_iteration tool do? +

Move a work item to a different iteration/sprint. It is categorised as a Write tool in the Azure 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 move_to_iteration? +

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

What risk level is move_to_iteration? +

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

Can I rate-limit move_to_iteration? +

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

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

move_to_iteration is provided by the Azure DevOps MCP Server MCP server (jaybird-us/azure-devops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.