The real workflow
Where Claude Code enters the work
A small software business may give an agent repository, terminal, package, and deployment access before formal approval boundaries exist.
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.
MCP servers and hooks can expose local commands, files, APIs, tokens, and external services to the agent.
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 small businesses
A small business can adopt AI faster than it documents ownership, permissions, retention, and incident steps, leaving important access decisions invisible. In this case, a business connector can turn an over-privileged account into a broad retrieval or action surface spanning customers, employees, projects, and internal operations.
A connector does not create data, but it can make existing account permissions available through a new interface. The safe question is not only whether the connector is trusted; it is whether the connected account is broader than the task requires.
The business has a named owner, a minimal approved scope, a repeatable review, and evidence it can use with staff, clients, and suppliers.
Context decision
Three questions before adding access
Who owns this AI workflow and can remove its access without waiting for a former employee or supplier?
Which customer, financial, employee, contract, credential, or production data categories are explicitly out of scope?
Can the business reconstruct what was connected, changed, or shared if a client or insurer asks tomorrow?
Evidence goal: Maintain one lightweight register showing the tool owner, approved purpose, connected systems, restricted data, review date, and response contact.
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
Review .mcp.json, managed settings, hooks, server commands, scopes, transports, and trust prompts.
- 3
Assign the decision and next review to the business owner or designated system owner; do not leave the access boundary as an unwritten assumption.
- 4
Remove unknown servers and sandbox each remaining integration with narrow paths and network destinations. Record the result without copying private content or raw credentials into the report.
Controls to apply
Reduce access before adding trust
Remove unknown servers and sandbox each remaining integration with narrow paths and network destinations.
Use a least-privilege account or service identity created for the specific workflow.
Separate read-only retrieval from write, send, share, delete, and financial actions.
Set a recurring owner and expiry date for every connector rather than leaving access permanent.
Decision rule
Know when a formal baseline is justified
If the assistant has no connectors, document that and keep it true. If it can retrieve or change business data across services, create an access map before adding another integration.
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