Can we enforce certain aws tags on CloudFormation stack level via Tagging policy

Question

can we enforce certain tags to be used while deploying the CloudFormation stack such that if someone doesn't provide those tags, they won't be able to deploy the stack in an AWS account?

what I am trying to do is to enforce certain tag patterns. for example, if anyone wants to deploy their stack they have to provide certain tags like

1. Project_Name
2. Owner
3. Stage

and further, is there any way we can enforce this tagging(to CloudFormation tags) at an org level via Tagging policy? so nobody can deploy those stacks if they haven't have those tags on stack level.

what this will does is it will enforce tagging on a stack level rather than resources' level. Since stacks can have multiple resources inside and you don't want to use the same tag under each resource. so we can require certain tags on the stack deployment level.

I do know that we can create a service control policy(SCP) for the AWS organization but can we use a tag policy for this use-case? and is that the right solution to implement this or is there any better way we can do this?