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

# AI Agent Access

Give AI agents secure, governed access to Keeper through MCP.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FrLAVbNCSHCZA6DWFkCKT%2FKeeper%20-%20AI%20Agent%20Access.jpg?alt=media&amp;token=66e6b8f4-d335-4ef3-bd1f-3f07320e479c" alt=""><figcaption></figcaption></figure>

The **AI Agent Access** feature controls how AI agents interact with Keeper through MCP. Users enable specific capabilities and select the folders and records available to each capability. An agent connection does not grant unrestricted access to the vault.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FEK9BRrs1PoNed9KJA7dV%2FScreenshot%202026-11-05%20at%201.46.32%E2%80%AFPM.png?alt=media&amp;token=9572d683-885e-41cf-9a02-e833a6cb5833" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Developer Center is currently in [Preview](https://docs.keeper.io/release-notes/desktop/web-vault-+-desktop-app/preview-release.md) and goes live with Vault Version 18.7
{% endhint %}

## Enable AI Agent Access

1. Sign in to Keeper Desktop and open **Developer Center**.
2. Select **AI Agent Access**.
3. Enable the **AI Agent Access** switch.
4. Review the capabilities under **Allowed Tools**.
5. Configure each required capability's guardrails before enabling its **Status** switch.
6. Select **MCP Setup** to connect an AI client. See [Set Up Keeper MCP](https://docs.keeper.io/keeperpam/developer-and-mcp/ai-agent-access/keeper-mcp-setup.md).

Use the **Connected Agents** control to review agent connections. Turn off **AI Agent Access** when MCP access is no longer required.

## Allowed capabilities

The interface labels capabilities according to their effect. **Read Only** identifies metadata discovery. **Modifies** identifies operations that change vault data or sharing. **High-Risk** identifies operations that require additional care, including deletion and PAM actions.

| Capability                                              | Label     | Purpose                                                                                                                               |
| ------------------------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| **Read records**                                        | Read Only | Find records and read safe metadata, such as titles and record types, within the allowed scope. Secret field values are not returned. |
| **Create & Update records**                             | Modifies  | Create or modify records containing passwords, API keys, URLs, and custom fields.                                                     |
| **Delete records**                                      | High-Risk | Move specified records to Deleted Items.                                                                                              |
| **Share records**                                       | Modifies  | Control record sharing and one-time shares.                                                                                           |
| **Share folders**                                       | Modifies  | Control shared folder permissions.                                                                                                    |
| **Request access to PAM resources**                     | High-Risk | Request access to protected PAM resources and use permitted access-management actions.                                                |
| **Execute KeeperPAM credential rotations**              | High-Risk | Rotate stored credentials on PAM resources, machines, and databases.                                                                  |
| **Execute KeeperPAM Database queries on PAM Databases** | High-Risk | Run permitted queries against PAM-managed databases. Write queries require a separate guardrail.                                      |

**Launch sessions and tunnels** and **Manage property file records** are labeled **Coming Soon** in the interface shown here. They are not part of the available-capability setup instructions. The database-query workflow has its own tunnel cleanup control.

## Configure guardrails

Guardrails are configured separately for each capability. Do not assume that selecting a folder for one capability selects it for every capability.

1. Click the gear icon in the capability's **Guardrails** column.
2. Select the operations needed for the workflow.
3. Use **Search Folders and Records**, or expand the folder tree, to select the permitted resources.
4. Select individual folders or records rather than **My Vault** when the workflow does not require vault-wide scope.
5. Click **Update**.
6. Review the capability's **Status** switch.

### Read records

The **Read records** guardrails include **Find records** and **Browse folders**, together with the folder and record scope.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2Fp4nf93amhXTQGbgSw5Xi%2FScreenshot%202026-11-05%20at%201.47.03%E2%80%AFPM.png?alt=media&amp;token=f4b1f700-46d8-4216-a75b-b8210fe79798" alt=""><figcaption><p>AI Agent Access - Guardrails</p></figcaption></figure>

Record discovery returns safe metadata. It does not return password or other secret field values. Permission to discover a PAM Database record also does not, by itself, authorize database queries.

### PAM access management

The **Request access to PAM resources** guardrails include:

* **Check access status**
* **Start approved access**
* **End access**

Select the PAM resources the agent may use. **Start approved access** applies to access that has already been approved; it is not permission to bypass an approval requirement.

### Credential rotation

The **Execute KeeperPAM credential rotations** guardrails include **Check rotation status** and **View rotation settings**, together with the resource scope. Enable this high-risk capability only for records intended for the rotation workflow.

### Database queries

The database-query guardrails include:

| Setting                     | Behavior                                                                                      |
| --------------------------- | --------------------------------------------------------------------------------------------- |
| **Allow write queries**     | When off, only read-only queries can run. Enable only when the workflow requires writes.      |
| **Maximum Rows per Query**  | Leave blank to use Keeper MCP's built-in 10,000-row limit, or enter a limit for the workflow. |
| **Close tunnels**           | Permit the agent to close database tunnels after use.                                         |
| Folder and record selection | Select the PAM Database resources available to the capability.                                |
|                             |                                                                                               |

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2F36WGFgwnD8JmJDdm1G9g%2FScreenshot%202026-11-05%20at%201.47.56%E2%80%AFPM.png?alt=media&amp;token=b5fcf674-c091-4aaf-9549-8e337d388895" alt=""><figcaption></figcaption></figure>

Read-only database access can still disclose sensitive business data. Limit the resource scope, returned rows, and database account privileges. Review what query results may be sent to the AI provider configured in the client.

See [Query PAM Databases with MCP](https://docs.keeper.io/keeperpam/developer-and-mcp/ai-agent-access/pam-database-queries-with-mcp.md) for the resource configuration and example workflow.

### Enterprise Role Enforcements

Keeper administrators can restrict **AI Agent Access** for users through **Roles → Enforcement Policies → AI Agent Access**. Admins can disable the feature entirely or limit which MCP tools are available.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FpzNXwPxho2vh66AGhXht%2FSome%20Settings%20Enabled.png?alt=media&amp;token=a181e933-f2c1-467a-b3cb-c83b9cea5ad1" alt=""><figcaption><p>AI Agent Access enforcement policies</p></figcaption></figure>


---

# 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.keeper.io/keeperpam/developer-and-mcp/ai-agent-access.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.
