Hi, not having specified which type of switch you're referring to I could only gave you generic few tips: apply ACL near to the source of the traffic (thus apply it to manage traffic of user's subnet 192.168.77.0) and, since ACL are generally stateless (on HPE/Aruba switches) start with on direction (traffic egressing the VLAN to "rest of the world")...this will translate to create an ACL which:
(1) permit 192.168.77.0 subnet to connect (IP or specific protocol/port <- it's up to your requirements) to specific destinations on Servers' subnet.
(2) deny 192.168.77.0 subnet to connect to any other internal segment (VLAN)
(3) permit 192.168.77.0 subnet to connect to any other network which is not denied before
(4) apply such ACL to the VLAN on the incoming direction (seen from the SVI interface on the routing Switch)
Clearly this applies if your Switch is the router for your network segments (subnets). Is it?
Then one could evaluate the case to create an ACL protecting the Server's subnet...but that is just an another step.
Pay attention on where you are to avoid locking you out.