Generate a single non-destructive audit payload with config, session, report, candidates, dry-run metrics and safety metadata.
AI agents call audit_bundle to retrieve information from Clean Process Ended without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool aggregates configuration, session data, reports, candidates, and dry-run metrics into a read-only audit bundle. It is explicitly described as non-destructive, meaning no side effects, writes, or deletions occur. This is purely a data retrieval and reporting operation.
From the tool's definition 'non-destructive audit payload' and 'dry-run metrics and safety metadata' — the tool explicitly states it only generates/reads audit information without modifying or deleting anything
Attacks that exploit this kind of access
Generate a single non-destructive audit payload with config, session, report, candidates, dry-run metrics and safety metadata. It is categorised as a Read tool in the Clean Process Ended MCP Server, which means it retrieves data without modifying state.
Register the Clean Process Ended MCP server in PolicyLayer and add a rule for audit_bundle: 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 Clean Process Ended. Nothing to install.
audit_bundle 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 audit_bundle 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 audit_bundle. 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.
audit_bundle is provided by the Clean Process Ended MCP server (marcelocaporale/clean-process-ended). 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 →