> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agentlinkops.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete disavow rule

> Remove one rule at its current revision.

`delete_disavow_rule`

Remove one rule at its current revision. Requires a signed-in owner or administrator. Monitoring history is retained.

<Note>Available in the deployed MCP and HTTP bundle. Confirm access and inputs with your connected catalog. Workspace scopes and enabled providers still apply.</Note>

| Access          | Behavior                                                   |
| --------------- | ---------------------------------------------------------- |
| `watches:write` | Writes or admits work; can change or remove existing state |

This operation changes saved state. Review its inputs and retry behavior before calling.

## Example request

Connect through [MCP](/guides/connect-mcp), [CLI](/guides/connect-cli), or [HTTP](/guides/connect-http). Replace example identifiers with records from your workspace.

<CodeGroup>
  ```json MCP theme={null}
  {
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "delete_disavow_rule",
      "arguments": {
        "projectId": "project_example",
        "ruleId": "rule_example",
        "revision": 1
      }
    }
  }
  ```

  ```bash CLI theme={null}
  agentlinkops call delete_disavow_rule --args '{"projectId":"project_example","ruleId":"rule_example","revision":1}'
  ```

  ```bash HTTP theme={null}
  curl "$AGENTLINKOPS_API_URL/v1/commands/delete_disavow_rule" \
    -H "Authorization: Bearer $AGENTLINKOPS_API_KEY" \
    -H 'Content-Type: application/json' \
    --data '{"projectId":"project_example","ruleId":"rule_example","revision":1}'
  ```
</CodeGroup>

## 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.

```json theme={null}
{
  "deleted": true,
  "rule_id": "dis_example",
  "revision": 3
}
```

## Input fields

Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.

| Field       | Type    | Presence | Meaning and constraints                                                                          |
| ----------- | ------- | -------- | ------------------------------------------------------------------------------------------------ |
| `projectId` | string  | Required | Identifier of the project returned by its create or list operation. minLength: 1; maxLength: 200 |
| `ruleId`    | string  | Required | Identifier of the rule returned by its create or list operation. minLength: 1; maxLength: 200    |
| `revision`  | integer | Required | Immutable set revision to read or compare. maximum: 9007199254740991; exclusiveMinimum: 0        |

### 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](/reference/schemas) explain evidence states, empty lists and extensions.

| Field      | Type    | Presence | Meaning and constraints                                                                                                 |
| ---------- | ------- | -------- | ----------------------------------------------------------------------------------------------------------------------- |
| `deleted`  | boolean | Required | must equal true                                                                                                         |
| `rule_id`  | string  | Required | Identifier returned by the related operation. minLength: 1; maxLength: 200                                              |
| `revision` | integer | Required | Optimistic concurrency revision; supply it as expectedRevision on the next write. minimum: 0; maximum: 9007199254740991 |

[Download input schema](/schemas/delete_disavow_rule.input.json) · [Download output schema](/schemas/delete_disavow_rule.output.json)

## 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](/reference/errors) 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](/reference/commands/list_disavow_rules) · [list\_disavow\_exports](/reference/commands/list_disavow_exports)

Follow the [related workflow](/guides/monitor-changes), inspect [capability status](/capability-status), or return to the [command index](/reference/index).