Add a discussion comment to a work item. Use to log agent reasoning or decisions.
AI agents use add_comment to create or update resources in Az Devops Cli — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Az Devops Cli environment.
Adding a comment creates new data and modifies the work item record, but the operation is fully reversible (comments can be deleted or edited). This places it in the Write category rather than Read (which would be retrieval-only) or Destructive (which cannot be undone).
From the tool's definition The tool description explicitly states 'Add a discussion comment to a work item', which is a create operation that modifies the work item by appending reversible data (a comment).
Attacks that exploit this kind of access
Add a discussion comment to a work item. Use to log agent reasoning or decisions. It is categorised as a Write tool in the Az Devops Cli MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Az Devops Cli MCP server in PolicyLayer and add a rule for add_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 Az Devops Cli. Nothing to install.
add_comment 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 add_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.
Set action: deny in the PolicyLayer policy for add_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.
add_comment is provided by the Az Devops Cli MCP server (praisesinkamba/az-devops-cli-mcp). 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 →