# FAQ

> Common questions about data access, permissions, and security for Holistics MCP Server.

Before diving in, one general clarification: MCP is an interface to Holistics features, not a separate system. It must be authenticated by a Holistics user account, and all of Holistics' data policies and access controls apply — whether you're using the UI, the API, or MCP.

## Permissions

### What permissions does MCP have in Holistics?

MCP inherits the permissions of the authenticated Holistics user — no more, no less. This includes data access, row-level permissions, and feature access. It behaves the same as using Holistics through the UI or API.

See [how queries are executed](/docs/ai/data-access-and-policy#how-queries-are-executed) for details.

### What is the recommended least-privilege setup?

Use OAuth authentication so each user connects under their own Holistics identity. This ensures everyone can only access the data their Holistics account permits — no shared credentials, no elevated access.

## Data

### What data does MCP return to the AI tool?

MCP can return real query results or metadata depending on your settings. You can control this — sample data and result data can each be turned off independently. Query results are currently capped at 1,000 rows.

Learn more in [Data access and policy](/docs/ai/data-access-and-policy#manage-data-access).

### Does MCP store or retain data?

MCP is a protocol, not a storage layer — it doesn't retain data on its own. Your AI tool or agent may retain data locally, but that's outside Holistics. Any data queried through MCP is handled the same way as queries made through the Holistics UI — retrieved and cached within your account's data center.

### Which data center does MCP use?

Each Holistics region has its own MCP server. Data is transferred through your account's regional MCP gateway, the same data center your Holistics account uses.

## Monitoring

### Is there audit logging for MCP queries?

Not yet exposed to users. Holistics currently has internal logging but it isn't directly accessible. If audit logging is important for your use case, reach out at [support@holistics.io](mailto:support@holistics.io).