list_change_request_comments
[Code Management] List comments on a change request. Supports filtering by comment type (GLOBAL_COMMENT or INLINE_COMMENT), state (OPENED or DRAFT), resolved status, and file path (for inline comments).
This record as markdown: /tools/alibabacloud-devops/list-change-request-comments.md
What list_change_request_comments does on Alibabacloud Devops
AI agents call list_change_request_comments to retrieve information from Alibabacloud Devops without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_change_request_comments is rated Low
This tool retrieves and queries existing comments on change requests with optional filters. It has no side effects, does not modify or delete data, and does not trigger external operations or financial transactions. It fits the 'Read' category as a pure data retrieval operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name includes 'list' and description states 'List comments on a change request' with filtering capabilities. No modification, deletion, execution, or financial operations are performed—only data retrieval.
Attacks that exploit this kind of access
The rule that runs list_change_request_comments safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Alibabacloud Devops, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_change_request_comments, this is the rule to start with:
list_change_request_comments is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Alibabacloud Devops, apply this rule, and every list_change_request_comments call is checked against it from then on.
Questions about list_change_request_comments
[Code Management] List comments on a change request. Supports filtering by comment type (GLOBAL_COMMENT or INLINE_COMMENT), state (OPENED or DRAFT), resolved status, and file path (for inline comments). It is categorised as a Read tool in the Alibabacloud Devops MCP Server, which means it retrieves data without modifying state.
Register the Alibabacloud Devops MCP server in PolicyLayer and add a rule for list_change_request_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 Alibabacloud Devops. Nothing to install.
list_change_request_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 list_change_request_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 list_change_request_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.
list_change_request_comments is provided by the Alibabacloud Devops MCP server (alibabacloud-devops-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Alibabacloud Devops, and thousands of servers like it.
This server
Across the catalogue