AI agents call list_package_repositories 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. |
perPage | number | — | Page size for pagination. Supports 1-100. Defaults to 100 when omitted. |
repoTypes | string | — | Comma-separated repository types: GENERIC, DOCKER, MAVEN, NPM, or NUGET. |
organizationId | string | — | Yunxiao organization ID. When omitted, the server uses the user's default organization. |
repoCategories | string | — | Comma-separated repository modes: Hybrid, Local, Proxy, ProxyCache, or Group. |
Parameters from the server's own tool schema.
This tool only queries and enumerates existing package repositories, returning metadata for discovery purposes. It has no side effects, does not execute operations, and does not modify or delete data. It is a straightforward read operation with minimal blast radius.
From the tool's definition Tool description states 'List artifact repositories' and 'to discover repository IDs' — pure data retrieval with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
List artifact repositories (Packages) in a Yunxiao organization. Use this to discover repository IDs for listing artifacts. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_package_repositories accepts 5 parameters: page, perPage, repoTypes, organizationId, repoCategories. 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_package_repositories: 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_package_repositories 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_package_repositories 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_package_repositories. 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_package_repositories 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 →