Retrieves all comments associated with a specific work item. Use this tool when you need to: - Review discussion history about a work item - See feedback or notes left by team members - Check if specific questions have been answered - Understand the context and evolution of a work item Args: id: ...
AI agents call get_work_item_comments to retrieve information from MCP Azure DevOps Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a retrieval operation with no side effects. It queries existing data (comments on a work item) without creating, modifying, deleting, or executing any operations. The severity is low because exposing comment retrieval to an AI agent poses minimal risk — the worst outcome is unauthorized information disclosure of internal discussions, which is mitigated by existing Azure DevOps access controls.
From the tool's definition Tool name 'get_work_item_comments' and description explicitly state it 'Retrieves all comments' with use cases focused on 'Review discussion history', 'See feedback or notes', and 'Check if specific questions have been answered' — all read-only query…
Documented attack patterns abuse exactly the kind of access get_work_item_comments gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Azure DevOps Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_work_item_comments:
{
"version": "1",
"default": "deny",
"tools": {
"get_work_item_comments": {}
}
}get_work_item_comments is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieves all comments associated with a specific work item. Use this tool when you need to: - Review discussion history about a work item - See feedback or notes left by team members - Check if specific questions have been answered - Understand the context and evolution of a work item Args: id: The work item ID project: Optional project name. If not provided, will be determined from the work item. Returns: Formatted string containing all comments on the work item, including author names, timestamps, and content, organized chronologically and formatted as markdown. It is categorised as a Read tool in the MCP Azure DevOps Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Azure DevOps Server MCP server in PolicyLayer and add a rule for get_work_item_comments: 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 Azure DevOps Server. Nothing to install.
get_work_item_comments is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_work_item_comments 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 get_work_item_comments. 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.
get_work_item_comments is provided by the MCP Azure DevOps Server MCP server (vortiago/mcp-azure-devops). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 MCP Azure DevOps Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 MCP Azure DevOps Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.