The real workflow
Where Claude Code enters the work
An agency coding agent can cross client boundaries when repositories, terminals, credentials, caches, or sessions are reused between engagements.
Claude Code is a local or cloud coding agent with file, command, network, MCP, and editing capabilities governed by permissions, sandboxing, trust, and account settings.
A local session can read client code and nearby files under the developer’s account, while account terms and API transport still matter.
Claude Code only has the permissions granted to it, but broad read access, bypass modes, unsandboxed commands, or overpowered MCP servers can make that boundary much wider than expected.
The presence of this path does not prove an incident. It identifies the boundary that should be checked before more sensitive context or authority is added.
Tool-specific boundary
Inspect the real access points.
What may carry context
repository and local file reads
edits and Bash commands
network access, MCP servers, hooks, and cloud environments
Settings to verify
Permission mode and deny rules
Filesystem and network sandbox
Trusted directories, MCP servers, hooks, and unsandboxed escape paths
Why this context matters
The consequence for agencies
Agency risk compounds when staff, contractors, shared tools, and reused credentials create paths between otherwise separate client environments. In this case, exposure can trigger contractual disputes, notification duties, account reviews, project delays, and costly investigation even when no malicious intent was involved.
Client data is not yours to expose simply because it helps complete a task. The practical question is whether the client authorized this tool, this account type, this data category, and this specific access path.
Every client remains isolated, access is attributable to a named operator, and the agency can deliver consistent evidence without revealing another client.
Context decision
Three questions before adding access
Can this operator or tool reach any repository, mailbox, drive, cache, token, or transcript belonging to another client?
Are credentials and AI sessions issued per client and person rather than shared across the agency?
Can the agency deliver useful proof to this client without including another client's names, paths, findings, or configuration?
Evidence goal: Create a separate client evidence record covering operator identity, workspace isolation, credentials, approved systems, review history, and delivery status.
A repeatable review
Four steps, no sensitive data required
- 1
Write down the exact Claude Code account, workspace, project, device, and connected service used in this workflow.
- 2
Confirm client authorization, account type, working directory, read-deny rules, retention choice, and network policy.
- 3
Assign the decision and next review to the client service owner or agency security lead; do not leave the access boundary as an unwritten assumption.
- 4
Use a client-specific OS workspace or container with only the approved repository mounted. Record the result without copying private content or raw credentials into the report.
Controls to apply
Reduce access before adding trust
Use a client-specific OS workspace or container with only the approved repository mounted.
Use separate client workspaces and least-privilege accounts instead of one shared personal AI context.
Minimize, redact, or synthesize data before it reaches the assistant.
Keep a simple register of approved tools, client constraints, access dates, and deletion steps.
Decision rule
Know when a formal baseline is justified
If a task contains client-confidential material, do not proceed on assumptions. CapitalGuard becomes useful when the work also involves repositories, connected tools, repeat client workflows, or evidence that must be shown back to the client.
CapitalGuard is relevant when the workflow includes repositories, recurring private work, credentials, connected systems, commands, or evidence that must be shared with another person. It does not inspect this account from the page or guarantee that an incident cannot occur.
Primary references