Skip to main content
propose_disavow_rule Propose one disavow rule. Activating a rule requires a signed-in owner or administrator; agent credentials cannot approve.
Available in the deployed MCP and HTTP bundle. Confirm access and inputs with your connected catalog. Workspace scopes and enabled providers still apply.
This operation changes saved state. Review its inputs and retry behavior before calling.

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 in structuredContent 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.
  • rules (array, required).
  • created (integer, required): True when this request created the record; false when an existing record was reused. minimum: 0; maximum: 9007199254740991
  • unchanged (integer, required): minimum: 0; maximum: 9007199254740991
  • revision (integer, required): Optimistic concurrency revision; supply it as expectedRevision on the next write. minimum: 0; maximum: 9007199254740991
Download input schema · Download output schema

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 include INVALID_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.

HTTP resource routes

This operation has no separate resource alias. Use its generic command route in a matching environment.

Continue

list_disavow_rules · list_disavow_exports Follow the related workflow, inspect capability status, or return to the command index.