You can do many things with the outbound traffic, and a simple first step is activation of CBWFQ default class FQ.

Inbound traffic is a problem. You can police it, but such policing is often after inbound traffic has already congested your WAN link. You can restrict the rate so much, you might avoid such inbound congestion, but doing this effectively often requires a very low cap.

Ideally, you want to manage congestion upstream, where the congestion forms, but this is often on the ISP equipment, and many are not receptive to doing so. (Of course, you might mention to your ISP if they're not receptive, you'll need to find a new ISP that is, but not as a bluff.)

PS:

Another tecnique for controlling inbound bandwidth usage, assuming traffic is TCP, is to shape outbound ACKs. Very tricky to do right, and inbound bandwidth usage can still vary. The big advantage of outbound ACK shaping, you can configure it much like outbound congestion management so it only has an effect when the total traffic goes over some cap, instead of an inbound policer limiting a class of traffic even when the bandwidth is available.