list_change_requests
[Code Management] List change requests with multi-condition filtering, pagination and sorting. Supports filtering by repository, author, reviewer, state (opened/merged/closed), search keywords, and creation time range.
This record as markdown: /tools/alibabacloud-devops/list-change-requests.md
What list_change_requests does on Alibabacloud Devops
AI agents call list_change_requests 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_requests is rated Low
This tool retrieves and queries existing change request data with no side effects. It supports filtering, pagination, and sorting but does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—an agent could retrieve change request information it shouldn't have access to, but cannot alter or act upon that data.
From the tool's definition Tool name 'list_change_requests' and description explicitly states 'List change requests' with filtering and pagination capabilities. No modification, deletion, or execution verbs present.
Attacks that exploit this kind of access
The rule that runs list_change_requests 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_requests, this is the rule to start with:
list_change_requests 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_requests call is checked against it from then on.
Questions about list_change_requests
[Code Management] List change requests with multi-condition filtering, pagination and sorting. Supports filtering by repository, author, reviewer, state (opened/merged/closed), search keywords, and creation time range. 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_requests: 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_requests 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_requests 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_requests. 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_requests 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