# Excluding specific fields from Forest Mongo version being returned under the hood

**URL:** https://community.forestadmin.com/t/excluding-specific-fields-from-forest-mongo-version-being-returned-under-the-hood/5522
**Category:** Feature suggestions
**Created:** [November 11, 2022, 12:01am UTC](https://community.forestadmin.com/t/excluding-specific-fields-from-forest-mongo-version-being-returned-under-the-hood/5522 "2022-11-11T00:01:56Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Nigel\_Fish](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/nigel_fish/32/5355_2.png) [@Nigel\_Fish](https://community.forestadmin.com/u/Nigel_Fish)
#### Post date: [November 11, 2022, 12:01am UTC](https://community.forestadmin.com/t/excluding-specific-fields-from-forest-mongo-version-being-returned-under-the-hood/5522/1 "2022-11-11T00:01:56Z")

</div>

## What is the feature?

I’m uncertain if anything exists for this, but I couldn’t help but notice that Forest Admin by default returns the entire object of any related data on things like list queries. E.g., if I have a list of Books, and those reference Authors, it provides an array of “included” in the query itself that provides the entire dataset of Authors which seems like a lot.

We have a way to excludeModels entirely, can we exludeFields from these object dumps?

## What problem does this solve for you?

Security / PII issues.

## Who else would be using this feature?

Anyone who cares about potential PII leakage issues.