Verify answers and sources
Claude can produce a convincing answer that is wrong, outdated, or missing context. For important facts, ask for primary sources and inspect them yourself. Do not base legal, medical, financial, security, or hiring decisions on a chat response alone; use qualified review and your organization’s process.
Limit sensitive data and access
Avoid uploading passwords, identity or payment numbers, customer records, trade secrets, and production keys unless there is an approved need. Redact files first and check account or workspace privacy settings. For Claude Code, integrations, and MCP, grant the least access needed, inspect file and command permissions, and confirm who can open shared links.
A practical safety checklist
A prompt, uploaded document, or web page can contain malicious instructions; do not treat untrusted text as an authoritative system command. Require human approval for sending external email, deleting records, or making purchases. Set a retention policy, report incorrect outputs, and keep logs and rollback options for important workflows.
Set boundaries for data and actions
Before uploading a file, remove identity, contact, payment, and customer details. Separate read permission from permission to change records, and require approval for external actions. Follow your organization’s retention and deletion policy and explain to users what they may share.
Security review prompt
Review this workflow for privacy, unnecessary data, excessive permissions, and irreversible actions. Rank the risks and identify steps that need human approval before execution.
Official sources
Claude features, plans, and usage limits can change; verify current details with official sources before purchasing or setting up a workflow.