New Adguard blocked apps and services to be enabled in the API by default

[mauriceatkinson]

Platform

Windows

Protocol

Regular

Do you use AdGuard app?

No I don't

Your configuration

I am using a fastapi backend server and making api calls to your adguard service. This allows me to automate the setting up of and adguard user, their devices and managing their policies.

Traceroute to AdGuard DNS

No response

Issue Details

I am using your api service to integrate into my parental control app. I have a policy to block all services but I have seen that when you add a new site into /oapi/v1/web_services you appear to have this enabled by default.

Expected Behavior

I expect that when new services get added to existing DNS server polices they inherit the policy default blocking behaviour and are not enabled by default.

Actual Behavior

When new services are added to /oapi/v1/web_services (like recently you added  copilot and io_interactive), they get automatically injected into existing DNS server policies with enabled: false instead of inheriting the policy's default blocking behaviour. For a parental control use case, new services should default to enabled: true (blocked) to match the existing policy configuration where all services are blocked.

Is this what you mean to happen or is it something you could change?

Screenshots

Additional Information

No response