AI agents call get_artifact 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 |
|---|---|---|---|
repoId | string | Yes | Packages repository ID. Use list_package_repositories to discover valid IDs. |
repoType | string | Yes | Repository type: GENERIC, DOCKER, MAVEN, NPM, NUGET, or PYPI. |
artifactId | string | Yes | Artifact ID (string or integer). Use list_artifacts 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 or queries artifacts from a repository. No modification, deletion, execution, or financial operation is performed. The action is read-only and non-destructive, consistent with the Read category for retrieval operations.
From the tool's definition Tool description states 'Get a specific artifact from a Packages repository by ID', with instruction to 'Use list_artifacts to discover valid artifact IDs'. The verb 'Get' and retrieval pattern indicate data retrieval without side effects.
Attacks that exploit this kind of access
Get a specific artifact from a Packages repository by ID. Use list_artifacts to discover valid artifact IDs. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_artifact accepts 4 parameters: repoId, repoType, artifactId, organizationId. Required: repoId, repoType, artifactId. 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 get_artifact: 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.
get_artifact 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 get_artifact 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 get_artifact. 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.
get_artifact 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 →