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

get_agent_artifact

Returns an agent-onboarding artifact shipped with a store template: system prompt, Agent Skills SKILL.md or MCP-config snippet. Pass slug for the RAW template artifact (before install, {{slot:...}} placeholders intact) or display_id for the display-bound artifact with placeholders resolved agains...

SERVERagentView SOURCEhttps://agentview.de/mcp
Low RISK CLASS
Category Read
Parameters 51 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/de-agentview-agentview-mcp/get-agent-artifact.md

What get_agent_artifact does on agentView

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

ParameterTypeRequiredDescription
key string Yes Artifact key, e.g. 'bot-system-prompt', 'agent-skill', 'mcp-config'.
slug string Template slug for the raw artifact. Provide slug OR display_id.
display_id string Display profile ID for the placeholder-resolved artifact. If both slug and display_id are given, display_id wins (substituted body).
access_token string Optional bearer token; prefer session_request_id.
session_request_id string Session handle from create_auth_session; pass it on every authenticated call.

Parameters from the server's own tool schema.

Why get_agent_artifact is rated Low

Even though get_agent_artifact only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsHandles credentials or secrets (access_token)

Questions about get_agent_artifact

What does the get_agent_artifact tool do? +

Returns an agent-onboarding artifact shipped with a store template: system prompt, Agent Skills SKILL.md or MCP-config snippet. Pass slug for the RAW template artifact (before install, {{slot:...}} placeholders intact) or display_id for the display-bound artifact with placeholders resolved against installed slots (ready to save, e.g. into ~/.claude/skills/). Discover keys via get_store_template_details (agentArtifacts array). Template mode needs no auth; display mode requires content scope and display ownership. It is categorised as a Read tool in the agentView MCP Server, which means it retrieves data without modifying state.

What parameters does get_agent_artifact accept? +

get_agent_artifact accepts 5 parameters: key, slug, display_id, access_token, session_request_id. Required: key. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_agent_artifact? +

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

What risk level is get_agent_artifact? +

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

Can I rate-limit get_agent_artifact? +

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

How do I block get_agent_artifact completely? +

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

What MCP server provides get_agent_artifact? +

get_agent_artifact is provided by the agentView MCP server (https://agentview.de/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on agentView, and thousands of servers like it.

// 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 agentView'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.