2026-09-20 AGY Permissions for MCP and Non-Workspace Access
What I set out to do
Resolve recurring permission prompts in Antigravity CLI (agy) when invoking MCP tools and accessing files across workspace boundaries.
What I actually did
- Diagnosed why agy was prompting for permissions:
- Antigravity defaults unconfigured MCP tools to
ask, andcoding-agents.nixonly populatedcommand(*)inallow. - Non-workspace access was disabled by default (
allowNonWorkspaceAccess = false), prompting on file access outside the git root.
- Antigravity defaults unconfigured MCP tools to
- Updated
nix/home-manager/modules/coding-agents/agy/agy.nix:- Configured
allowNonWorkspaceAccess = true;inprograms.antigravity-cli.settings.
- Configured
- Updated
nix/home-manager/modules/coding-agents/common/coding-agents.nix:- Added
lib.optional cfg.enableMcp "mcp(*)"toprograms.antigravity-cli.permissions.allow. - Generalized
toAgyPatternto check for existing parentheses so arbitrary tool patterns are not wrapped intocommand(...).
- Added
- Updated
nix/tests/coding-agents-contract.nix:- Added assertions ensuring
mcp(*)is inallowandallowNonWorkspaceAccessis true forantigravity-cli.
- Added assertions ensuring
- Verified formatting and test contracts using
just check. - Applied changes via
hm switchand committed as0a82907(feat(agy): allow mcp tools and non-workspace access).
What was striking
- Antigravity’s permission evaluator treats
allowNonWorkspaceAccessas an explicit settings key at the top level ofsettings.json, while tool authorizations follow theaction(target)DSL inpermissions.allow.