New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

artifact_fetch

Fetch a file's bytes from an allowed location (a discovered project root, ~/.yaver/artifacts, or YAVER_ARTIFACT_ROOTS) so a compiled PDF, a .dwg, a screenshot or a build output can reach you. Images come back as a viewable image block; other files as base64 + mime + size + sha256, bounded at 12 MB.

SERVERYaver SOURCEyaver-cli
Low RISK CLASS
Category Read
Parameters 31 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/artifact-fetch.md

What artifact_fetch does on Yaver

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

ParameterTypeRequiredDescription
path string Yes Absolute path (or ~/…) inside an allowed root.
machine string — Owned device to read from (default: local).
maxBytes integer — Optional lower cap (hard max 12 MB).

Parameters from the server's own tool schema.

Why artifact_fetch is rated Low

Retrieves file data from whitelisted directories with no side effects or destructive capabilities.

From the tool's definition Fetch a file's bytes from an allowed location, no modifications, bounded 12 MB.

Risk signalsAccepts file system path (path) · Admin/system-level operation

Questions about artifact_fetch

What does the artifact_fetch tool do? +

Fetch a file's bytes from an allowed location (a discovered project root, ~/.yaver/artifacts, or YAVER_ARTIFACT_ROOTS) so a compiled PDF, a .dwg, a screenshot or a build output can reach you. Images come back as a viewable image block; other files as base64 + mime + size + sha256, bounded at 12 MB. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does artifact_fetch accept? +

artifact_fetch accepts 3 parameters: path, machine, maxBytes. Required: path. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on artifact_fetch? +

Register the Yaver MCP server in PolicyLayer and add a rule for artifact_fetch: 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 Yaver. Nothing to install.

What risk level is artifact_fetch? +

artifact_fetch is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit artifact_fetch? +

Yes. Add a rate_limit block to the artifact_fetch 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.

How do I block artifact_fetch completely? +

Set action: deny in the PolicyLayer policy for artifact_fetch. 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.

What MCP server provides artifact_fetch? +

artifact_fetch is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Yaver, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Yaver's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.