Show recent sanitization history from the ledger.
AI agents call view_ledger to retrieve information from Query Sanitizer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries historical sanitization records from an internal ledger. It performs no modifications, deletions, or external operations. The data it accesses (redaction history) is informational metadata used for auditing and transparency of the DLP system's operations.
From the tool's definition Tool name is 'view_ledger' and description states 'Show recent sanitization history from the ledger.' The verb 'Show' and the read-only nature of viewing historical ledger entries indicate data retrieval with no side effects.
Attacks that exploit this kind of access
Show recent sanitization history from the ledger. It is categorised as a Read tool in the Query Sanitizer MCP Server, which means it retrieves data without modifying state.
Register the Query Sanitizer MCP server in PolicyLayer and add a rule for view_ledger: 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 Query Sanitizer. Nothing to install.
view_ledger 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 view_ledger 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 view_ledger. 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.
view_ledger is provided by the Query Sanitizer MCP server (vidoluco/query-sanitizer-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 →