Export all events for a subject_id as a signed JSON-L file (GDPR Art. 20 portability). Returns an R2 presigned URL valid for 1 hour.
AI agents call export_dossier to retrieve information from Audit event mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and exports existing audit log data for a given subject_id — a read/query operation. No data is created, modified, or deleted. However, severity is medium because the exported dossier may contain sensitive personal or audit data about an individual, and the presigned URL could expose that data to unintended parties if misused by an AI agent.
From the tool's definition Export all events for a subject_id as a signed JSON-L file (GDPR Art. 20 portability). Returns an R2 presigned URL valid for 1 hour.
Attacks that exploit this kind of access
Export all events for a subject_id as a signed JSON-L file (GDPR Art. 20 portability). Returns an R2 presigned URL valid for 1 hour. It is categorised as a Read tool in the Audit event mcp MCP Server, which means it retrieves data without modifying state.
Register the Audit event MCP server in PolicyLayer and add a rule for export_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 Audit event mcp. Nothing to install.
export_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 export_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 export_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.
export_dossier is provided by the Audit event MCP server (mightbesaad/audit-event-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 →