explain_artefact
AI agents call explain_artefact to retrieve information from Orionbelt Semantic Layer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'explain_artefact' most likely retrieves or describes properties of a semantic model artefact (similar to describe_model or get_model on the same server), making it a Read operation. Severity is medium rather than low because the semantic layer provides access to potentially sensitive business logic, metrics, and data schemas that could inform further attacks.
From the tool's definition Tool name 'explain_artefact' suggests inspection/retrieval of artefact metadata or documentation. Description is empty, limiting certainty.
Attacks that exploit this kind of access
explain_artefact. It is categorised as a Read tool in the Orionbelt Semantic Layer MCP Server, which means it retrieves data without modifying state.
Register the Orionbelt Semantic Layer MCP server in PolicyLayer and add a rule for explain_artefact: 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 Orionbelt Semantic Layer. Nothing to install.
explain_artefact 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 explain_artefact 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 explain_artefact. 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.
explain_artefact is provided by the Orionbelt Semantic Layer MCP server (ralfbecher/orionbelt-semantic-layer-mcp). 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 →