AI agents call list_pipeline_jobs_by_category to retrieve information from Yunxiao without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
category | string | Yes | Task category. Common value: DEPLOY (for deployment tasks). |
pipelineId | string | Yes | Pipeline ID. Use list_pipelines to discover valid IDs. |
organizationId | string | — | Yunxiao organization ID. When omitted, the server uses the user's default organization. |
Parameters from the server's own tool schema.
This tool retrieves and displays structured information about pipeline jobs without creating, modifying, executing, or deleting any resources. It is a passive query operation on DevOps pipeline metadata. The blast radius of misuse is minimal — at worst, an AI agent gains visibility into pipeline structure, which poses no direct operational risk.
From the tool's definition Tool description states 'List jobs (tasks) within a Flow pipeline grouped by category' — a listing/enumeration operation with no modification or execution of those jobs.
Attacks that exploit this kind of access
List jobs (tasks) within a Flow pipeline grouped by category. Use this after identifying a pipeline to see its build, deploy, and test stages. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_pipeline_jobs_by_category accepts 3 parameters: category, pipelineId, organizationId. Required: category, pipelineId. The full parameter table on this page comes from the server's own tool schema.
Register the Yunxiao MCP server in PolicyLayer and add a rule for list_pipeline_jobs_by_category: 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 Yunxiao. Nothing to install.
list_pipeline_jobs_by_category 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_pipeline_jobs_by_category 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_pipeline_jobs_by_category. 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_pipeline_jobs_by_category is provided by the Yunxiao MCP server (@futuretea/yunxiao-mcp-server). 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 →