Client - Option to Disable Policy Distribution

When onboarding a new client, we typically don't want our scripts making changes until we have our agents deployed, have a lay of the land, and have made sure the incumbent provider has all of their software remove - or we removed it for them. When relying heavily on tagging for scripted automations and deployments, these will kick off upon agent install as the tags are applied once data is retrieved; almost immediately. Without the described feature, the only way I can think of to get around this is to configure a custom field checkbox for "Policy Deployment Enabled", a single script that sets a registry entry depending on the state of the custom field, a tag based on that registry entry, and then modify all other policies to include that tag as required for distribution.