---
title: "Sensitive actions, confirmations and revocation"
canonical: https://www.billabex.com/en/help/billabex-with-ai/sensitive-actions-confirmations-revocation/
lang: en
alternate: https://www.billabex.com/fr/aide/billabex-avec-ia/actions-sensibles-confirmations-revocation.md
updated: 2026-09-27
index: https://www.billabex.com/llms.txt
---

# Sensitive actions, confirmations and revocation

<section class="help-summary" aria-labelledby="in-short"><h2 id="in-short">In short</h2><p>An MCP action can send or modify a communication, change an account, handle a task, or adjust a setting. Before confirming, review the tool name, organization, target, and every value. Avoid permanent approval for write tools. If anything is unclear, reject the call; you can revoke consent and reconnect the client with fewer rights.</p></section>

## Expected result

No sensitive modification runs without an explicit target, visible parameters, and informed human confirmation.

## Before you start

- The client must show tool calls and request approval for write operations.
- Know where to disconnect the client and revoke its Billabex consent.

## Procedure

1. Read the proposed tool name and description before reviewing the assistant’s drafted response.
2. Check the organization, account or task identifier, recipients, content, and amounts.
3. Reject grouped or ambiguous actions and request a narrower operation.
4. Confirm the correctly parameterized call once; do not enable permanent approval to save a few clicks.
5. After temporary or suspicious use, disconnect the client on the AI side.
6. In Billabex, open **My account**, **Connected applications** section, then click **Cut access** next to the application and confirm.

## What Billabex does

Billabex scopes prevent a write tool from running under read-only consent. The AI client controls how confirmation is displayed, so security also depends on its approval settings and human review.

The **Connected applications** section lists every application you gave access to, with its authorization date and its access in plain words. Cutting access removes your authorization, then revokes its tokens: the cut may not be instant. If you build your own integration, the **My OAuth clients** section on the same page lets you create, edit, renew the secret of or delete your clients.

## If the result is not what you expected

- If the tool or its parameters are hidden, cancel and use Billabex directly.
- After an unexpected action, record the time, organization, and target before revoking access.
- Right after a cut, the application may still get through for a few moments: its tokens are revoked in the background.
- A reconnection creates new consent: review the scopes instead of automatically reusing previous ones.