Surface non-code knowledge from the index: DB schemas (migrations, ORM models), API specs (routes, OpenAPI endpoints), infrastructure (docker-compose services, K8s resources), CI pipelines (jobs, stages), and config (env vars). All data from the existing index — no extra I/O. Use to discover infr...
AI agents call get_artifacts to retrieve information from Trace without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and queries pre-indexed metadata about code infrastructure and configuration. It has no side effects—all data comes from the existing index with no file reads or external operations triggered. It is a pure read/retrieval operation, making it the lowest risk category.
From the tool's definition Tool description explicitly states 'Read-only' and 'no extra I/O'. It 'surfaces' and 'discovers' existing indexed knowledge (DB schemas, API specs, infrastructure, CI pipelines, config) and 'returns JSON'.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access get_artifacts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Trace, and nothing reaches the server without passing your rules. This is the rule we recommend for get_artifacts:
{
"version": "1",
"default": "deny",
"tools": {
"get_artifacts": {}
}
}get_artifacts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Surface non-code knowledge from the index: DB schemas (migrations, ORM models), API specs (routes, OpenAPI endpoints), infrastructure (docker-compose services, K8s resources), CI pipelines (jobs, stages), and config (env vars). All data from the existing index — no extra I/O. Use to discover infrastructure and config artifacts without reading files. Read-only. Returns JSON: { artifacts: [{ category, kind, name, file }], total }. It is categorised as a Read tool in the Trace MCP Server, which means it retrieves data without modifying state.
Register the Trace MCP server in PolicyLayer and add a rule for get_artifacts: 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 Trace. Nothing to install.
get_artifacts 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_artifacts 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_artifacts. 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_artifacts is provided by the Trace MCP server (nikolai-vysotskyi/trace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 178 Trace tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
178 Trace tools catalogued and risk-classified — across an index of 42,500+ MCP servers.