I'm afraid this kind of transaction rule can't be implemented in a simple way in MultiChain. But there is a way to make it possible: to have incoming funds to an address not be immediately spendable, and for the recipient to have to conduct a second transaction (which you could automate in the application) to make the funds spendable, by using up a "receiving limit" which is stored in some inline metadata output which the user has control over. The spendability limits could be enforced on-chain with a transaction filter.
The ability to change these limits would be tricky right now, but a new smart filter related feature we are currently implementing, and which will be available in the next protocol upgrade, will make it easy.