So just to re-iterate. The MDC cannot be limited, if there are 100,000 items in your archive, you will get all 100,000 items downloaded as stubs (i.e. subject, sender, recipients, sent date, 250 chars of the body etc), typically very small stubs of the email.
The Vault Cache (DB Files) can be limited based on a maximum size or a percentage and older items will either be removed from the Vault Cache (not from the online archive) or not downloaded at all.
For Virtual Vault / MDC Size control you can do things like stop people from archiving items (dragging items from a PST or their mailbox in to Virtual Vault) or how many items they can drag drop before it stops allowing more items to be dragged and dropped until a sync has occurred
You can also have it trigger an archive upload if a certain amount is awaiting to be archived, that way you keep the MDC size small and get the items archived ASAP and decrease the chances of dataloss
Settings are found in the Desktop Policy, any time you change these the user would need to be synchronized and their vault cache reset, because the settings are written as Registry keys, and they override what the policy is set to.
VAULT CACHE:
Maximum store size
The maximum size, in megabytes, that an offline archive is allowed to occupy.
Percentage store size
Percentage of disk capacity to use for Vault Cache.
If neither 'Store size' nor 'Percentage store size' is specified a default value of 10% of disk capacity is used.
VIRTUAL VAULT:
Users can archive items
Controls whether users can archive items.
Max item size to archive
Controls the maximum size (in MB) of an item that can be moved or copied into Virtual Vault.
(0) No limit
Max total size of items to archive
Controls the maximum total size (in MB) of pending-archive data in Vault Cache.
(0) No limit
Threshold total size of items to trigger synchronization
Specifies the total size (in MB) of pending-archive items that triggers automatic Vault Cache synchronization.
(0) Disabled