Read one generated artifact by snapshot_id and path. Requires access to the snapshot and may return snapshot-not-found, invalid-path, or artifact-not-found errors. Example: snapshot_id=abc-123, path=AGENTS.md. Use this when you need the full text of one artifact. Use get_snapshot instead when you...
AI agents call get_artifact to retrieve information from AXIS iliad without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns the content of a previously generated artifact by snapshot ID and path. It has no capability to modify, delete, or execute anything—it only queries and returns data. The error states it can return indicate read-only access patterns. This is a straightforward data retrieval operation with no destructive or executable capabilities.
From the tool's definition Tool description explicitly states 'Read one generated artifact' and 'when you need the full text of one artifact'. The verb 'get' and the phrase 'read' clearly indicate retrieval without modification.
Attacks that exploit this kind of access
Read one generated artifact by snapshot_id and path. Requires access to the snapshot and may return snapshot-not-found, invalid-path, or artifact-not-found errors. Example: snapshot_id=abc-123, path=AGENTS.md. Use this when you need the full text of one artifact. Use get_snapshot instead when you first need the artifact list. It is categorised as a Read tool in the AXIS iliad MCP Server, which means it retrieves data without modifying state.
Register the AXIS iliad 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 AXIS iliad. 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 AXIS iliad MCP server (lastmanupinc-hub/axis-iliad). 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 →