Added
-
grantry install --gatedmakes grantry the agent's only credential source. It writes project-scope files that blank the ambientAWS_*variables in the agent's own shell and setGRANTRY_CALLER=agent, and adds a short steering note telling the agent to fetch credentials via theget_credentialsMCP tool. It does not ban theawscommand — the agent still runsaws/boto3, just only with the short-lived, policy-checked credentials grantry issues. Written per client where supported (Claude Codesettings.json, the VS Code forks'terminal.integrated.env); Copilot CLI and Claude Desktop get the steering note only. Idempotent and scoped to the current directory.This is defense-in-depth, not a guarantee: it cannot remove
~/.aws/credentials, the SSO cache, or an instance role, and does not control network egress. For a hard boundary, run the agent with no ambient AWS access at all. The command says so plainly.