> For the complete documentation index, see [llms.txt](https://docs.trustlogix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trustlogix.io/trust-ai/ai-agents/access-policies.md).

# Access Policies

Access policies for AI Agents are created on "resources"

## Create & Deploy Policy

* To create an AI Agent access policy, navigate to the desired AI Agent and go to the **Access Policies** tab
* Click **Create Policy** and provide a name and description, then click **Next.**
* Next, select the desired **Resource Source** for the policy

{% hint style="warning" %}
Currently, only Data Sources & Data Products are supported discoverable resource sources.
{% endhint %}

* After selecting the desired **Resources**, click **Next**. 
* Policy conditions can be made with respect to **Resource Attributes** and **User Attributes/Entitlements**
* After saving and deploying the policy, the policy will be evaluated and decision returned dynamically to the AI Agent when it requests access to the resource via MCP. See [MCP Server](/trust-ai/mcp-server.md) for more details.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.trustlogix.io/trust-ai/ai-agents/access-policies.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.