# How to verify that a redaction is complete Verify a redaction with an AI agent over MCP: read the redacted copy back as text, check annotations and metadata, and inspect the pages. A redaction you have not verified is a claim, not a control. Verification costs a few calls and is the difference between *"the tool ran"* and *"the data is gone"*. {{< alert style="info" >}} The commands and config snippets on this page are for the **.NET** build of the server — the only platform available today. Installation and client setup: [MCP server for .NET]({{< ref "redaction/net/mcp/_index.md" >}}). Other platforms will expose the same tools with their own launch command; everything else on this page applies unchanged. {{< /alert >}} ## 1. Read the redacted copy back as text > Extract the text of case-file_redacted.pdf and tell me whether any email address appears in it. Use a tool that returns text, such as `extract_text` on the [GroupDocs.Parser MCP server](https://docs.groupdocs.com/parser/mcp.md) (Docker only). Expect **none**. A hit means the pattern missed variants — a different separator, a line break, a different case — or the run hit the evaluation cap. Do not re-run `redact_text` for this check: it returns a saved file, not a count, and writes another copy. ## 2. Check the other three places > Now check the redacted copy for annotations and read its document properties. [`redact_annotations`]({{< ref "redaction/mcp/tools-reference/redact-annotations.md" >}}) and [`erase_metadata`]({{< ref "redaction/mcp/tools-reference/erase-metadata.md" >}}) applied in the pass do not prove they were applied to **this** file — the chaining rule means it is entirely possible to verify a document that skipped a step. Check the file you are about to release, not the one you think you produced. Annotations and properties do not show up in a text read-back. `get_annotations` on the [GroupDocs.Annotation MCP server](https://docs.groupdocs.com/annotation/mcp.md) lists the annotations that remain, and `read_metadata` on the [GroupDocs.Metadata MCP server](https://docs.groupdocs.com/metadata/mcp.md) reads the document properties, including EXIF, XMP and IPTC. ## 3. Look at the pages Area redactions cannot be verified by pattern. Open the document, or have the agent render the affected pages with `render_page` on the [GroupDocs.Viewer MCP server](https://docs.groupdocs.com/viewer/mcp.md), and confirm each box covers what it was meant to cover — completely, on the right page. ## 4. Confirm the licence state of the run that produced it > What is the license status of the redaction server? If the answer is `evaluation`, the redaction was capped at four replacements and the verification above will usually show it — but a document with exactly four matches would pass and still be wrong. Licence first, verify second; both, every time. [Licensing]({{< ref "redaction/mcp/getting-started/licensing.md" >}}). ## Keep the evidence The verification transcript — patterns used, files produced, and what the read-back found — is the record that shows the redaction was performed and checked. Ask the agent for it as a summary and keep it with the case file: > Summarize what you redacted, in which file, and what the verification found. ## What verification cannot tell you It cannot tell you whether your **patterns were the right ones**. Everything above proves that what you asked to be removed is gone. Deciding what should be removed is your judgement, and it remains the part of redaction that no tool takes off your hands. ## Read more * [Trust no redaction you haven't verified](https://blog.groupdocs.com/redaction/verify-redaction-complete-ai-agent-mcp/) — the same scenario on the GroupDocs blog, with worked examples and the trade-offs.