> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/references/interfaces/ai-activation/authentication-and-authorization.md).

# Authentication and authorization

MCP defines how clients and servers exchange messages. Authentication and authorization are enforced by the MCP server implementation and the transport configuration used to reach it.

## How Data Product MCP enforces access

Every request is evaluated using the caller's DataOS identity.

If a user cannot access a Data Product, table, column, or value in DataOS, the assistant cannot access it through Data Product MCP. If a value is masked for the user in DataOS, the assistant receives the masked value.

This keeps the assistant inside the same governance boundary as every other DataOS interface.

## What the server does on each request

Data Product MCP:

1. Authenticates the caller.
2. Authorizes the requested operation.
3. Applies Data Product policies.
4. Returns only the response the caller is allowed to receive.

The host can improve the conversation around the answer. It does not expand the user's access.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://v2.dataos.info/references/interfaces/ai-activation/authentication-and-authorization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.