# get_artifact

[Packages Management] Get information about a single artifact in a package repository

Agent View of the PolicyLayer registry record for `get_artifact`. HTML page: https://policylayer.com/tools/alibabacloud-devops/get-artifact

## Facts

- Tool: `get_artifact`
- Server: Alibabacloud Devops (`alibabacloud-devops-mcp-server`) — https://policylayer.com/tools/alibabacloud-devops.md
- Install: `npx -y alibabacloud-devops-mcp-server`
- Homepage: git+ssh://git@github.com/aliyun/alibabacloud-devops-mcp-server.git
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_artifact",
    "arguments": {}
  }
}
```

## Why get_artifact is rated Low

This tool retrieves or queries artifact metadata from a package repository. The verb 'get' and the phrase 'get information' clearly indicate a read-only operation. There is no modification, deletion, execution, or financial impact. The blast radius of misuse is minimal—an attacker could only learn about artifact existence or properties, not alter systems or data.

From the tool's own definition: "Tool name 'get_artifact' combined with description 'Get information about a single artifact in a package repository' indicates a retrieval operation with no side effects."

## Use case

AI agents call get_artifact to retrieve information from Alibabacloud Devops without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Alibabacloud Devops:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_artifact": {}
  }
}
```

## Other tools on Alibabacloud Devops (201)

- `cancel_app_release_stage_execution` — Destructive — https://policylayer.com/tools/alibabacloud-devops/cancel-app-release-stage-execution.md
- `cancel_appstack_change_request` — Destructive — https://policylayer.com/tools/alibabacloud-devops/cancel-appstack-change-request.md
- `delete_app_orchestration` — Destructive — https://policylayer.com/tools/alibabacloud-devops/delete-app-orchestration.md
- `delete_branch` — Destructive — https://policylayer.com/tools/alibabacloud-devops/delete-branch.md
- `delete_file` — Destructive — https://policylayer.com/tools/alibabacloud-devops/delete-file.md
- `delete_flow_variable_group` — Destructive — https://policylayer.com/tools/alibabacloud-devops/delete-flow-variable-group.md
- `delete_resource_member` — Destructive — https://policylayer.com/tools/alibabacloud-devops/delete-resource-member.md
- `delete_tag` — Destructive — https://policylayer.com/tools/alibabacloud-devops/delete-tag.md
- `delete_tag_group` — Destructive — https://policylayer.com/tools/alibabacloud-devops/delete-tag-group.md
- `delete_testcase` — Destructive — https://policylayer.com/tools/alibabacloud-devops/delete-testcase.md
- `delete_variable_group` — Destructive — https://policylayer.com/tools/alibabacloud-devops/delete-variable-group.md
- `delete_version` — Destructive — https://policylayer.com/tools/alibabacloud-devops/delete-version.md
- `execute_app_release_stage` — Execute — https://policylayer.com/tools/alibabacloud-devops/execute-app-release-stage.md
- `execute_job_action` — Execute — https://policylayer.com/tools/alibabacloud-devops/execute-job-action.md
- `execute_pipeline_job_action` — Execute — https://policylayer.com/tools/alibabacloud-devops/execute-pipeline-job-action.md
- `execute_pipeline_job_run` — Execute — https://policylayer.com/tools/alibabacloud-devops/execute-pipeline-job-run.md
- `execute_system_release_stage` — Execute — https://policylayer.com/tools/alibabacloud-devops/execute-system-release-stage.md
- `pass_app_release_stage_validate` — Execute — https://policylayer.com/tools/alibabacloud-devops/pass-app-release-stage-validate.md
- `pass_pipeline_validate` — Execute — https://policylayer.com/tools/alibabacloud-devops/pass-pipeline-validate.md
- `refuse_app_release_stage_validate` — Execute — https://policylayer.com/tools/alibabacloud-devops/refuse-app-release-stage-validate.md
- `refuse_pipeline_validate` — Execute — https://policylayer.com/tools/alibabacloud-devops/refuse-pipeline-validate.md
- `rerun_pipeline_job_run` — Execute — https://policylayer.com/tools/alibabacloud-devops/rerun-pipeline-job-run.md
- `resume_vm_deploy_order` — Execute — https://policylayer.com/tools/alibabacloud-devops/resume-vm-deploy-order.md
- `retry_app_release_stage_pipeline` — Execute — https://policylayer.com/tools/alibabacloud-devops/retry-app-release-stage-pipeline.md
- `retry_pipeline_job_run` — Execute — https://policylayer.com/tools/alibabacloud-devops/retry-pipeline-job-run.md
- `retry_vm_deploy_machine` — Execute — https://policylayer.com/tools/alibabacloud-devops/retry-vm-deploy-machine.md
- `skip_app_release_stage_pipeline` — Execute — https://policylayer.com/tools/alibabacloud-devops/skip-app-release-stage-pipeline.md
- `skip_pipeline_job_run` — Execute — https://policylayer.com/tools/alibabacloud-devops/skip-pipeline-job-run.md
- `skip_vm_deploy_machine` — Execute — https://policylayer.com/tools/alibabacloud-devops/skip-vm-deploy-machine.md
- `stop_pipeline_job_run` — Execute — https://policylayer.com/tools/alibabacloud-devops/stop-pipeline-job-run.md
- …and 171 more: https://policylayer.com/tools/alibabacloud-devops.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=alibabacloud-devops · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/alibabacloud-devops