add_work_item_comment · Azure DevOps MCP Server MCP

WHAT IT DOES

What add_work_item_comment does on Azure DevOps MCP Server

AI agents use add_work_item_comment 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 add_work_item_comment needs a policy

Adding a comment is a reversible write operation that creates new data without executing code, triggering external actions, deleting data, or moving money. The impact is low-severity because comments are typically non-critical metadata that can be edited or deleted by authorized users, and an AI misusing this tool would only clutter work items with unwanted comments rather than cause systemic damage.

From the tool's definition Tool name is 'add_work_item_comment' and description states it 'Add[s] a comment to a work item.' This creates new data (a comment) within an existing work item.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_work_item_comment Rate-limited

add_work_item_comment 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": {
    "add_work_item_comment": {
      "limits": [
        {
          "counter": "add_work_item_comment_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 add_work_item_comment

What does the add_work_item_comment tool do? +

Add a comment to a work item. 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 add_work_item_comment? +

Register the Azure DevOps MCP Server MCP server in PolicyLayer and add a rule for add_work_item_comment: 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 add_work_item_comment? +

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

Can I rate-limit add_work_item_comment? +

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

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

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