AI agents call dossier to retrieve information from Loom without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'dossier' and the partial description 'Load Art' suggest a read operation (loading/retrieving data), consistent with the server's purpose of providing persistent identity and memory. However, the description is severely truncated, lowering confidence.
From the tool's definition Tool name: 'dossier', description: 'Load Art\' — description appears truncated/incomplete
Attacks that exploit this kind of access
Load Art\. It is categorised as a Read tool in the Loom MCP Server, which means it retrieves data without modifying state.
Register the Loom MCP server in PolicyLayer and add a rule for dossier: 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 Loom. Nothing to install.
dossier 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 dossier 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 dossier. 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.
dossier is provided by the Loom MCP server (jbarket/loom). 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 →