Read the local process ledger summary, recent snapshot metadata, and recent cleanup events.
AI agents call ledger_read 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.
This tool retrieves historical and summary data about processes and cleanup events. It has no side effects, does not execute code, does not modify state, and does not delete or move resources. The read-only nature and inspection-focused context of the server confirm this is a safe data retrieval function.
From the tool's definition Tool name contains 'read' and description states 'Read the local process ledger summary, recent snapshot metadata, and recent cleanup events' — purely retrieval operations with no modification or execution.
Attacks that exploit this kind of access
Read the local process ledger summary, recent snapshot metadata, and recent cleanup events. 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 ledger_read: 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.
ledger_read 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 ledger_read 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 ledger_read. 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.
ledger_read 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 →