终止发布流程
AI agents invoke AbolishPipelineRun to trigger actions in Alibabacloud Dataworks. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
Id | string | Yes | 发布流程的唯一标识 |
ProjectId | number | Yes | DataWorks工作空间的ID |
Parameters from the server's own tool schema.
AbolishPipelineRun triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
终止发布流程. It is categorised as a Execute tool in the Alibabacloud Dataworks MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
AbolishPipelineRun accepts 2 parameters: Id, ProjectId. Required: Id, ProjectId. The full parameter table on this page comes from the server's own tool schema.
Register the Alibabacloud Dataworks MCP server in PolicyLayer and add a rule for AbolishPipelineRun: 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 Dataworks. Nothing to install.
AbolishPipelineRun is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the AbolishPipelineRun 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 AbolishPipelineRun. 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.
AbolishPipelineRun is provided by the Alibabacloud Dataworks MCP server (alibabacloud-dataworks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.