list_disavow_exports
List dated disavow export receipts with content hashes and source rule revisions.
Available in the deployed MCP and HTTP bundle. Confirm access and inputs with your connected catalog. Workspace scopes and enabled providers still apply.
This read does not start a verification job.
Example request
Connect through MCP, CLI, or HTTP. Replace example identifiers with records from your workspace.Returned result
Illustrative data validated against the documented response schema. IDs and dates are examples, not a live account capture. MCP returns this data instructuredContent and in a text content block; generic HTTP and CLI return the JSON result directly.
Input fields
Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.Validation and omitted values
Proposals are inert until a human owner or administrator approves them. Agent credentials cannot approve, reject or delete rules. Export records deterministic active-rule content and its hash; it never submits a file to Google.Output fields
Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.receipts(array, required).cursor(string / null, required).
All fields and nested objects
All fields and nested objects
Errors and retries
The command is annotated idempotent. Reuse an accepted idempotency key when the input provides one; changing the payload under a reused key can conflict. Operation-specific errors includeINVALID_DISAVOW_INPUT, HUMAN_ADMIN_REQUIRED, DISAVOW_NOT_READY, DISAVOW_REVISION_CONFLICT, DISAVOW_RULE_NOT_FOUND, DISAVOW_RULE_CONFLICT, DISAVOW_SCOPE_CLOSED, DISAVOW_CAPACITY, DISAVOW_EXPORT_CAPACITY, DISAVOW_IMPORT_TOO_LARGE, DISAVOW_RULE_TOO_LARGE, INVALID_CURSOR.
See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.