Some tools only read information. Others create drafts, update records, send messages, publish content or delete information. Read the tool description and the agreed permission scope before asking for a change.
Start with a draft#
For a new workflow, prepare the intended output before applying it. Check the target account, destination, content and timing. If a tool cannot create a draft, ask the AI to prepare the content in conversation and stop before the live action.
Prepare a proposed update for record TEST-001 using the approved
fields. Show the exact changes and target workspace. Do not save
the update until the authorised decision-maker approves it.This is a workflow instruction, not a built-in approval feature. A prompt alone cannot replace enforced permissions or a product's own approval controls.
Verify the destination#
Check the organisation, brand, recipient or record ID. A correct message sent from the wrong account is still a failed task. For scheduled actions, include the date, time and timezone explicitly.
Avoid duplicate actions#
If a request times out, an upstream service may already have accepted it. Before retrying a send, publish, payment-related operation or record creation, inspect the resulting state. If the tool does not expose a safe check, contact DigLab rather than guessing.
Confirm the outcome#
A useful completion record includes the operation, source-system identifier, final state and time. For a publish operation, confirm the published destination. For an update, retrieve the changed record. For an asynchronous job, distinguish submitted from completed.
Actions outside the agreed scope#
New spending, new recipients, bulk changes, important deletion and expanded access require their own authorised scope. MCP DigLab does not turn a general chat request into permission to act across every connected business system.