AI agents call list_artifacts 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 |
|---|---|---|---|
page | number | — | Page number for pagination. Starts at 1. |
sort | string | — | Sort direction: asc or desc. |
repoId | string | Yes | Packages repository ID. Use list_package_repositories to discover valid IDs. |
search | string | — | Package name search text. |
orderBy | string | — | Sort field: latestUpdate or gmtDownload. |
perPage | number | — | Page size for pagination. Supports 1-100. Defaults to 100 when omitted. |
repoType | string | Yes | Repository type: GENERIC, DOCKER, MAVEN, NPM, NUGET, or PYPI. |
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 or queries artifact data from a repository without creating, modifying, deleting, or executing operations. It is a straightforward listing/enumeration function typical of DevOps platforms for artifact inventory inspection. The blast radius of misuse is minimal—an agent could only view artifact metadata, not modify or delete artifacts or trigger deployments.
From the tool's definition Tool name 'list_artifacts' and description 'List artifacts in a Packages repository' indicate a retrieval operation with no modification or side effects. The dependency on 'list_package_repositories' for input further confirms this is a read-only query.
Attacks that exploit this kind of access
List artifacts in a Packages repository. Requires a repository ID from list_package_repositories. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_artifacts accepts 8 parameters: page, sort, repoId, search, orderBy, perPage, repoType, organizationId. Required: repoId, repoType. 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_artifacts: 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_artifacts 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_artifacts 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_artifacts. 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_artifacts 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 →