Permissions

A Claude Code run completes while a cleanup gate revokes a temporary cloud role, token, and MCP session before handoff

Claude Code finished. Its temporary cloud access did not

A completed Claude Code run can leave cloud roles, tokens, and MCP sessions behind. Require a cleanup receipt that proves temporary authority has gone.

Claude Code compacts its conversation while an external control-state checkpoint preserves authority, denied actions, pending effects, and evidence bindings

Keep Claude Code's safety state outside its context window

Context compaction can preserve the task while losing the decision that blocked a dangerous tool call. Store authority, denials, and unresolved effects in a control checkpoint outside the transcript.

Three individually valid Claude Code MCP reads are rejected because their source versions form a mixed production snapshot

Reject a Claude Code plan built from a mixed snapshot

Claude Code can read three correct facts and still build a plan for a system state that never existed. Record a coherent read set and reject evidence that crosses a consistency boundary.

A human approval becomes a single-use capability bound to one Claude Code operation, and the tool gateway rejects any replay after redemption

Treat Claude Code approval as a single-use capability

A human approval should authorize one exact Claude Code effect, not every retry that follows. Issue a single-use capability and record its redemption at the tool gateway.

MCP tool output is labelled untrusted, reduced to evidence, checked against the original Claude Code scope, and recorded in a reviewable trace

Do not let MCP tool output rewrite Claude Code's instructions

An MCP response can contain instruction-shaped text that pushes Claude Code beyond its approved task. Put a trust boundary between tool evidence and agent authority.

Stopping Claude Code does not cancel queued MCP work

A stopped Claude Code run can leave queued MCP calls and provider jobs alive. Use a cancellation barrier to revoke authority, drain pending work, and prove the run is quiet.

A Claude Code run pins an MCP capability manifest and stops when the live server schema, implementation, target scope, or side effects differ

Pin the MCP tool contract before Claude Code uses it

An MCP method can keep the same name while its schema, target scope, or side effects change. Pin a capability manifest so Claude Code cannot inherit a different tool after approval.

Preview uses restricted access, a boundary test checks denied writes, and execution requires separate approval

Run the agent in shadow mode before it changes anything

An agent’s preview is useful only if the boundary prevents writes. Review the proposed actions, then test the permissions behind the preview.

A Claude Code permission workflow where request, grant, and evidence lead to automatic expiry

Claude Code permissions need expiry dates

Claude Code permissions are safest when they are temporary. Treat every extra file, command, MCP tool, and network path as a task-scoped grant that must expire unless a human renews it with evidence.