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

# Redact Call

> Use the redact_call MCP tool on the DialNexa remote MCP server.

<span data-api-safety-label="destructive"><Badge color="red" size="sm" shape="pill">Destructive</Badge></span>

Permanently masks a call's TRANSCRIPT and RECORDING while keeping the call record itself (status, duration, cost, outcome) intact. This is the tool for privacy and data-deletion requests — "delete the recording for that call", "remove what the caller said", a GDPR erasure ask. It CANNOT be undone and the audio is not recoverable, so never use it to tidy up or free space, and never as a side effect of another request. Requires confirm: true. If the user only wants to stop seeing it, say that this is irreversible and ask them to confirm that is what they want.

## Parameters

| Name      | Type      | Required | Description                                                                                                      |
| --------- | --------- | -------- | ---------------------------------------------------------------------------------------------------------------- |
| `call_id` | `string`  | Yes      | The call ID, e.g. call\_abc123                                                                                   |
| `confirm` | `boolean` | Yes      | Must be true. Set this only after the user has explicitly approved erasing this call's transcript and recording. |

## Before you call

* Connect and initialize the MCP client with OAuth or an API key for the intended workspace.
* Provide the required parameters: `call_id`, `confirm`.
* Set `confirm: true` only after the user approves the exact target and action.

## Example MCP request

Send `tools/call` after your client completes MCP initialization. Replace placeholder values with IDs and inputs from your workspace. For object and array parameters, follow the nested requirements in the parameter description instead of treating an empty value as complete.

```json theme={null}
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "redact_call",
    "arguments": {
      "call_id": "VALUE",
      "confirm": true
    }
  }
}
```

The server returns one text content block. Parse `content[0].text` as JSON when the tool succeeds. See [MCP responses and errors](/docs/mcp-tools/errors) for the full envelope and failure behavior.

## Verify the result

Confirm the response is not marked `isError`. Call [List Calls](/docs/mcp-tools/calls/list-calls) to read the affected resource. Verify that the target is removed or disconnected before reporting completion.

## Retry safety

This tool can remove or disconnect a resource. Confirm the exact target first, and do not retry after an uncertain result until you verify the current state.

## Related MCP tools

* [List Calls](/docs/mcp-tools/calls/list-calls): `list_calls`
* [Get Call](/docs/mcp-tools/calls/get-call): `get_call`

## Related guides

* [Connect to the DialNexa MCP server](/docs/mcp-tools/overview)
* [Calls MCP tools](/docs/mcp-tools/calls/overview)
* [MCP responses and errors](/docs/mcp-tools/errors)