Here is a config example to block specific peer(s) when using VPLS BGP style.

I finished the same tests and got a working vrf-import policy to block specific peer(s) and allow the rest of them.

root@router# show policy-options policy-statement test | display set 

set policy-options policy-statement test term 1 from neighbor <1.1.1.1> --------------------> IBGP neighbor IP address

set policy-options policy-statement test term 1 from community prueba

set policy-options policy-statement test term 1 then reject

set policy-options policy-statement test term 2 from community prueba

set policy-options policy-statement test term 2 then accept

[edit]

root@router# show policy-options community prueba | display set 

set policy-options community prueba members target:26617:9917 ----------------> VPLS instance vrf-target

root@router# show routing-instances vpls | display set 

set routing-instances vpls protocols vpls site-range 100

set routing-instances vpls protocols vpls no-tunnel-services

set routing-instances vpls protocols vpls site ce-1 site-identifier 2

set routing-instances vpls instance-type vpls

set routing-instances vpls interface ge-0/0/2.3561

set routing-instances vpls route-distinguisher 10.20.131.2:9917

set routing-instances vpls vrf-import test

set routing-instances vpls vrf-target target:26617:9917

Currently, the above configuration is blocking peer 1.1.1.1, here is the "show vpls connections" output. I used the same verf-target as in your routers.

root@router# run show vpls connections 

Layer-2 VPN connections:

Instance: vpls

Edge protection: Not-Primary

 Local site: ce-1 (2)

  connection-site      Type St   Time last up     # Up trans

  3             rmt  Up   Apr 9 10:16:34 2024      1

   Remote PE: 3.3.3.3, Negotiated control-word: No

   Incoming label: 262147, Outgoing label: 262146

   Local interface: lsi.1049856, Status: Up, Encapsulation: VPLS

    Description: Intf - vpls vpls local site 2 remote site 3

   Flow Label Transmit: No, Flow Label Receive: No