TL;DR: Claude Code managed settings are a policy-design problem, Willow reports, because the file can govern commands, secrets, MCP access, and network reach at the system level. MDM-backed controls only work when teams define defaults before developers start using the tool.
Editorial analysis by NHI Mgmt Group, based on content published by Willow: “Claude Code Policy: Write Managed Settings Fast”.
Key questions
Q: Why do managed settings matter more than local developer settings?
A: Managed settings matter because they are enforced at the system level through MDM, while local settings can be changed or bypassed by the user.
Q: How should teams decide whether to allow MCP servers in developer tooling?
A: Allow MCP servers only when they are centrally reviewed, inventory is known, and the policy can constrain which servers the agent may reach.
Q: What should security teams block first in Claude Code policies?
A: Start with the highest-risk runtime actions: shell commands that can move data, access credentials, or alter repositories.
Practitioner guidance
- Define a baseline policy tier first Choose minimal, standard, strict, or lockdown before editing individual rules so teams are not inventing governance from a blank file.
- Block high-risk commands by default Deny or gate commands such as curl, wget, sudo, git push, scp, and rsync until there is a clear business need and approval path.
- Restrict secrets and credential file access Prevent the agent from reading .env files, secrets directories, SSH keys, AWS credentials, and service-account files unless the workflow truly requires it.
Bottom line: Claude Code governance is really a policy-design problem, because the managed-settings file controls commands, secrets, MCP access, and network reach at the system level.
Glossary terms: Managed Settings, MCP Server, Policy Baseline, Shadow AI
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Policy baseline is the real control plane for AI coding agents: The article shows that the hard problem is not whether Claude Code can be governed, but whether teams can operationalize a stable policy before adoption spreads. That is the same governance pattern NHI teams face with any high-privilege software identity: if the default posture is unclear, the rollout becomes the control failure. The practitioner lesson is to treat policy design as a prerequisite to deployment, not a cleanup step after users start working.
A few things that frame the scale:
- Claude Code-assisted commits leaked secrets at a rate of 3.2%, more than double the human-only baseline of 1.5%, with peaks reaching 31 secrets per 1,000 commits in August 2025, according to the State of Secrets Sprawl 2026.
- 52% of respondents see AI security decision-making power shifting toward platform and infrastructure teams rather than the executive suite, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What is the safest rollout model for AI coding agent governance?
A: Use a baseline, deploy it centrally, and then relax controls only where the workflow proves necessary. That approach avoids one-off exceptions and gives security teams a repeatable way to manage secrets access, command execution, and network reach as usage expands.
👉 Read our full editorial: Claude Code managed settings need a policy baseline before rollout