> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Drata

The Drata connector lets your AI agent act in each user's Drata account. Each user connects their own Drata access token once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 30 tools.

**Authentication:** Bearer Token
**Categories:** Monitoring
**Tools:** 30: 26 read, 4 write, 0 destructive
**Users sign in with:** Access token
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=DRATA)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Drata connection

   In **AgentKit > Connections**, create a Drata connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'drata'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Drata:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'drata_company_get',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "drata"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Drata:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="drata_company_get",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their Drata credentials there. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'drata_company_get',
  toolInput: {},
  connector: 'drata',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="drata_company_get",
    tool_input={},
    connection_name="drata",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `drata_company_get`

Get Company · Read-only

Get the Drata account's company profile.
Returns the company name, legal name, domain, description, training and background-check settings, and entitlements.
Use this to confirm which Drata account the connection uses.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `drata_control_get`

Get Control · Read-only

Get one control in a Drata workspace by ID.
Returns the control's code, name, description, question, activity, rationale, framework tags, owners, linked requirement, test and evidence IDs, and timestamps.
Use this when you have a control ID. Use drata_controls_list to find one.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `controlId` (`string`, required): The ID of the control. Get it from drata_controls_list. Example: 101.
- `workspaceId` (`integer`, required): The ID of the Drata workspace. Get it from drata_workspaces_list. Example: 1.
- `cursor` (`string`, optional): This parameter is used to paginate through results. No value is needed for the first request. If there are additional results, the response will contain a `pagination.cursor` value that can be used in the subsequent request to retrieve the next page of results. Example: eyJpZCI6MTAwfQ==.
- `expand` (`array`, optional): List of subcollections and sub-objects to expand. Valid values: customFields, evidenceIds, flags, frameworkTags, owners, requirements, testIds, topics. Example: ["customFields"].
- `size` (`integer`, optional): Number of results to return. Example: 50.
- `sort` (`string`, optional): Which field to sort by. Example: createdAt. One of: `createdAt`, `updatedAt`.
- `sortDir` (`string`, optional): The direction to sort the data. Example: ASC. One of: `ASC`, `DESC`.

Example input: `{"controlId":"<controlId>","workspaceId":1}`

### `drata_control_owners_list`

List Control Owners · Read-only

List the users who own a Drata control.
Returns each owner's user id, name and email.
Use this to find who is responsible for a control.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `controlId` (`integer`, required): The ID of the control. Get it from drata_controls_list. Example: 101.
- `workspaceId` (`integer`, required): The ID of the Drata workspace. Get it from drata_workspaces_list. Example: 1.
- `cursor` (`string`, optional): This parameter is used to paginate through results. No value is needed for the first request. If there are additional results, the response will contain a `pagination.cursor` value that can be used in the subsequent request to retrieve the next page of results. Example: eyJpZCI6MTAwfQ==.
- `excludeUserIds` (`array`, optional): User IDs of the Control Owners to exclude. Example: [].
- `frameworkSlug` (`string`, optional): Filter data by Users associated with this Control Requirement Framework slug. Example: soc2.
- `includeTotalCount` (`boolean`, optional): Include total count of all matching records in response. Only honored on first page (when cursor is null). Example: false.
- `includeUserIds` (`array`, optional): User IDs of the Control Owners to return. Example: [1, 2, 3].
- `size` (`integer`, optional): Number of results to return. Example: 50.
- `sort` (`string`, optional): Which field to sort by. Example: createdAt. One of: `createdAt`, `updatedAt`.
- `sortDir` (`string`, optional): The direction to sort the data. Example: ASC. One of: `ASC`, `DESC`.

Example input: `{"controlId":101,"workspaceId":1}`

### `drata_control_requirements_list`

List Control Requirements · Read-only

List the framework requirements mapped to a Drata control.
Returns each requirement's id, name, description and framework, with pagination.
Use this to see which framework requirements a control satisfies.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `controlId` (`integer`, required): The ID of the control. Get it from drata_controls_list. Example: 101.
- `workspaceId` (`integer`, required): The ID of the Drata workspace. Get it from drata_workspaces_list. Example: 1.
- `cursor` (`string`, optional): This parameter is used to paginate through results. No value is needed for the first request. If there are additional results, the response will contain a `pagination.cursor` value that can be used in the subsequent request to retrieve the next page of results. Example: eyJpZCI6MTAwfQ==.
- `excludeIds` (`array`, optional): Exclude requirements by array of IDs. Example: [].
- `frameworkSlug` (`string`, optional): Filter data by controls associated with these framework slugs. This parameter is intended to be used only for custom frameworks. Example: slug.
- `frameworkTag` (`array`, optional): Filter data by controls associated with these framework tags. Valid values include NONE, SOC_2, ISO27001, CCPA, GDPR, HIPAA, PCI, SCF, NIST80053, NISTCSF, CMMC, NIST800171 and more. Example: ["SOC_2", "ISO27001"].
- `includeTotalCount` (`boolean`, optional): Include total count of all matching records in response. Only honored on first page (when cursor is null). Example: false.
- `size` (`integer`, optional): Number of results to return. Example: 50.
- `sort` (`string`, optional): Which field to sort by. Example: createdAt. One of: `createdAt`, `updatedAt`.
- `sortDir` (`string`, optional): The direction to sort the data. Example: ASC. One of: `ASC`, `DESC`.

Example input: `{"controlId":101,"workspaceId":1}`

### `drata_controls_list`

List Controls · Read-only

List the controls in a Drata workspace, filtered by readiness, monitoring, evidence, policy, test results or approval status.
Returns each control's id, code, name, description, framework tags, owners and linked test and evidence IDs, with a cursor for the next page.
Use this to review control status. Use drata_control_get for one control.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `workspaceId` (`integer`, required): The ID of the Drata workspace. Get it from drata_workspaces_list. Example: 1.
- `cursor` (`string`, optional): This parameter is used to paginate through results. No value is needed for the first request. If there are additional results, the response will contain a `pagination.cursor` value that can be used in the subsequent request to retrieve the next page of results. Example: eyJpZCI6MTAwfQ==.
- `expand` (`array`, optional): List of subcollections and sub-objects to expand. Valid values: customFields, evidenceIds, flags, frameworkTags, owners, requirements, testIds, topics. Example: ["customFields"].
- `hasEvidence` (`boolean`, optional): Filter to Controls with or without Evidence. Example: true.
- `hasPassingTest` (`boolean`, optional): Filter to Controls with at least one passing Test. Example: true.
- `hasPolicy` (`boolean`, optional): Filter to Controls with or without Policy. Example: true.
- `includeTotalCount` (`boolean`, optional): Include total count of all matching records in response. Only honored on first page (when cursor is null). Example: false.
- `isArchived` (`boolean`, optional): Filter Controls that are or are not archived. Example: false.
- `isEnabled` (`boolean`, optional): Filter Controls that are or are not enabled. Example: true.
- `isMonitored` (`boolean`, optional): Filter Controls that have or do not have a Monitor. Example: false.
- `isReady` (`boolean`, optional): Filter Controls that are or are not ready. Example: false.
- `policyId` (`integer`, optional): The ID of the policy. Get it from drata_policies_list. Example: 301.
- `requiredApprovals` (`string`, optional): Filter Controls by the status of their required approval. CHANGES_REQUESTED, NEEDS_APPROVAL and PREPARE_FOR_APPROVERS identify Controls that are not ready because their approval is still in progress; APPROVED and NO_REVIEW do not block readiness. Approval status only applies to enabled Controls, so this filter cannot be combined with isEnabled=false. Example: PREPARE_FOR_APPROVERS. One of: `PREPARE_FOR_APPROVERS`, `NEEDS_APPROVAL`, `APPROVED`, `CHANGES_REQUESTED`, `NO_REVIEW`.
- `size` (`integer`, optional): Number of results to return. Example: 50.
- `sort` (`string`, optional): Which field to sort by. Example: createdAt. One of: `createdAt`, `updatedAt`.
- `sortDir` (`string`, optional): The direction to sort the data. Example: ASC. One of: `ASC`, `DESC`.
- `ticketStatus` (`string`, optional): Only include Controls with an associated Task Management Ticket. Example: IN_PROGRESS. One of: `IN_PROGRESS`, `ARCHIVED`.

Example input: `{"workspaceId":1}`

### `drata_events_list`

List Events · Read-only

List Drata events (the audit trail of changes, test runs and syncs), filtered by type, source, category, connection, user, workspace or date.
Returns each event's id, type, category, source, description, user and time, with a cursor for the next page.
Use this to see what changed recently in Drata.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `category` (`string`, optional): Filter data to events of this category. Valid values include AUTOPILOT, AGENT, POLICY, PERSONNEL, REPORT, VENDOR, ASSET, COMPANY, ASSESSMENT, AUDIT, MONITOR, USER and more. Example: AUTOPILOT.
- `connectionId` (`integer`, optional): The connection to filter events by. A null/blank value will return events without a connection. Example: 123.
- `createdAtEndDate` (`string`, optional): Filters the events to those with a creation date less than or equal to this date and time. Example: 2026-01-15.
- `createdAtStartDate` (`string`, optional): Filters the events to those with a creation date greater than or equal to this date and time. Example: 2026-01-15.
- `cursor` (`string`, optional): This parameter is used to paginate through results. No value is needed for the first request. If there are additional results, the response will contain a `pagination.cursor` value that can be used in the subsequent request to retrieve the next page of results. Example: eyJpZCI6MTAwfQ==.
- `expand` (`array`, optional): List of subcollections and sub-objects to expand. Valid values: connection, issues, metadata, testId, testName, user. Example: ["connection"].
- `includeTotalCount` (`boolean`, optional): Include total count of all matching records in response. Only honored on first page (when cursor is null). Example: false.
- `size` (`integer`, optional): Number of results to return. Example: 50.
- `sort` (`string`, optional): Events can only be sorted by create date. Example: createdAt. One of: `createdAt`.
- `sortDir` (`string`, optional): The direction to sort the data. Example: ASC. One of: `ASC`, `DESC`.
- `source` (`string`, optional): Filter data to events of this source. Example: APP. One of: `APP`, `AUTOPILOT`, `PUBLIC_API`, `VENDOR_QUESTIONNAIRE`, `SCHEDULED`, `WORKFLOW`, `DRATA_POLICY`, `AUDIT_AGENT`, `DRATA_MIGRATION`.
- `type` (`string`, optional): Filter data to events of this type. Valid values include COMPANY_DATA_UPDATED, COMPANY_LOGO_UPDATED, COMPANY_KEY_PERSONNEL_UPDATED, COMPANY_ROLES_UPDATED, COMPANY_SECURITY_DATA_UPDATED, COMPANY_DOCUMENT_UPLOADED, COMPANY_DOCUMENT_DOWNLOADED, COMPANY_DOCUMENT_DELETED, COMPANY_HUMAN_RESOURCES_DATA_UPDATED, EMPLOYMENT_STATUS_UPDATED, REMINDER_EMAIL_SENT, POLICIES_DOWNLOAD_ALL and more. Example: COMPANY_DATA_UPDATED.
- `userId` (`integer`, optional): The Drata user ID. Get it from drata_users_list. Example: 456.
- `workspaceId` (`integer`, optional): The ID of the Drata workspace. Get it from drata_workspaces_list. Example: 1.

Example input: `{}`

### `drata_evidence_artifacts_list`

List Evidence Artifacts · Read-only

List the artifacts (files, URLs or text) attached to a Drata evidence item.
Returns each artifact's id, name, extension, version, source, type and dates, with pagination.
Use this to see what has been uploaded as proof for an evidence item.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `evidenceId` (`integer`, required): The ID of the evidence item. Get it from drata_evidence_list. Example: 789.
- `workspaceId` (`integer`, required): The ID of the Drata workspace. Get it from drata_workspaces_list. Example: 1.
- `artifactTypes` (`array`, optional): Filter artifacts by type. Valid values: URL, S3_FILE, TICKET_PROVIDER, NONE, GOOGLE_DRIVE, ONE_DRIVE, BOX, DROPBOX, SHARE_POINT, TEST_RESULT. Example: ["URL"].
- `cursor` (`string`, optional): This parameter is used to paginate through results. No value is needed for the first request. If there are additional results, the response will contain a `pagination.cursor` value that can be used in the subsequent request to retrieve the next page of results. Example: eyJpZCI6MTAwfQ==.
- `isArchived` (`boolean`, optional): True returns only archived (past) artifacts, false only active ones. Omit to return both. Example: false.
- `name` (`string`, optional): Filter artifacts by name (prefix match). Example: Q4-2024-Security-Audit.
- `size` (`integer`, optional): Number of results to return. Example: 50.
- `sort` (`string`, optional): Which field to sort by. Example: createdAt. One of: `createdAt`, `updatedAt`.
- `sortDir` (`string`, optional): The direction to sort the data. Example: ASC. One of: `ASC`, `DESC`.

Example input: `{"evidenceId":789,"workspaceId":1}`

### `drata_evidence_get`

Get Evidence · Read-only

Get one evidence item in a Drata workspace by ID.
Returns the evidence item's name, description, implementation guidance, status, renewal date and schedule, owners, artifacts and linked controls.
Use this when you have an evidence ID. Use drata_evidence_artifacts_list for its files and links.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `evidenceId` (`integer`, required): The ID of the evidence item. Get it from drata_evidence_list. Example: 789.
- `workspaceId` (`integer`, required): The ID of the Drata workspace. Get it from drata_workspaces_list. Example: 1.
- `expand` (`array`, optional): List of subcollections and sub-objects to expand. Valid values: owners, artifacts, controls. Example: ["owners"].

Example input: `{"evidenceId":789,"workspaceId":1}`

### `drata_evidence_list`

List Evidence · Read-only

List the evidence items in a Drata workspace, filtered by name, owner, framework, status or artifact type.
Returns each evidence item's id, name, description, status, renewal date and schedule, owners, artifacts and linked controls, with a cursor for the next page.
Use this to check evidence status. Use drata_evidence_get for one item.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `workspaceId` (`integer`, required): The ID of the Drata workspace. Get it from drata_workspaces_list. Example: 1.
- `artifactTypes` (`array`, optional): Filter evidence items by artifact types. Valid values: URL, S3_FILE, TICKET_PROVIDER, NONE, GOOGLE_DRIVE, ONE_DRIVE, BOX, DROPBOX, SHARE_POINT, TEST_RESULT. Example: ["URL"].
- `cursor` (`string`, optional): This parameter is used to paginate through results. No value is needed for the first request. If there are additional results, the response will contain a `pagination.cursor` value that can be used in the subsequent request to retrieve the next page of results. Example: eyJpZCI6MTAwfQ==.
- `evidenceStatuses` (`array`, optional): Filter evidence items by statuses. Valid values: NEEDS_ARTIFACT, EXPIRED, EXPIRING_SOON, TEST_ERROR, TEST_FAILED, READY, TEST_PASSED, TEST_UNUSED, TEST_DISABLED, TEST_DELETED. Example: ["NEEDS_ARTIFACT"].
- `expand` (`array`, optional): List of subcollections and sub-objects to expand. Valid values: owners, artifacts, controls. Example: ["owners"].
- `frameworkIds` (`array`, optional): Array of Ids of frameworks to be used as filters. Example: [1, 2, 3].
- `name` (`string`, optional): Filter evidence items by name (prefix match). Example: SOC2 Evidence.
- `ownerIds` (`array`, optional): IDs of the users that own the evidence current version. Example: [1, 2, 3].
- `size` (`integer`, optional): Number of results to return. Example: 50.
- `sort` (`string`, optional): Which field to sort by. Example: createdAt. One of: `createdAt`, `updatedAt`.
- `sortDir` (`string`, optional): The direction to sort the data. Example: ASC. One of: `ASC`, `DESC`.

Example input: `{"workspaceId":1}`

### `drata_framework_requirements_list`

List Framework Requirements · Read-only

List the requirements of one framework in a Drata workspace.
Returns each requirement's id, code, name, description, category, framework and mapped controls, with pagination.
Use this to review a framework's requirements. Use drata_control_requirements_list to go from a control to its requirements.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `frameworkId` (`integer`, required): The ID of the framework. Get it from drata_frameworks_list. Example: 3.
- `workspaceId` (`integer`, required): The ID of the Drata workspace. Get it from drata_workspaces_list. Example: 1.
- `cursor` (`string`, optional): This parameter is used to paginate through results. No value is needed for the first request. If there are additional results, the response will contain a `pagination.cursor` value that can be used in the subsequent request to retrieve the next page of results. Example: eyJpZCI6MTAwfQ==.
- `excludeIds` (`array`, optional): Exclude Requirements by array of IDs. Example: [].
- `expand` (`array`, optional): List of subcollections and sub-objects to expand. `controls` includes a limited subcollection of Controls mapped to each Requirement. `customFields` includes Custom Field values for each Requirement. `framework` includes a compact Framework object on each Requirement. Valid values: controls, customFields, framework. Example: ["controls"].
- `includeTotalCount` (`boolean`, optional): Include total count of all matching records in response. Only honored on first page (when cursor is null). Example: false.
- `isInScope` (`boolean`, optional): Filter Requirements that are or are not in scope (not archived). Example: true.
- `isReady` (`boolean`, optional): Filter Requirements that are or are not ready. Example: false.
- `size` (`integer`, optional): Number of results to return. Example: 50.
- `sort` (`string`, optional): Which field to sort by. Example: createdAt. One of: `createdAt`, `updatedAt`.
- `sortDir` (`string`, optional): The direction to sort the data. Example: ASC. One of: `ASC`, `DESC`.

Example input: `{"frameworkId":3,"workspaceId":1}`

### `drata_frameworks_list`

List Frameworks · Read-only

List the compliance frameworks (such as SOC 2, ISO 27001 or HIPAA) in a Drata workspace.
Returns each framework's id, name, tag, readiness counts and whether it is enabled, with pagination.
Use this to find a framework ID and see overall readiness.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `workspaceId` (`integer`, required): The ID of the Drata workspace. Get it from drata_workspaces_list. Example: 1.
- `cursor` (`string`, optional): This parameter is used to paginate through results. No value is needed for the first request. If there are additional results, the response will contain a `pagination.cursor` value that can be used in the subsequent request to retrieve the next page of results. Example: eyJpZCI6MTAwfQ==.
- `excludeIds` (`array`, optional): Array of Framework IDs to exclude from results. Example: [1, 2, 3].
- `includeTotalCount` (`boolean`, optional): Include total count of all matching records in response. Only honored on first page (when cursor is null). Example: false.
- `isEnabled` (`boolean`, optional): Filter Frameworks by enabled state. Example: true.
- `isReady` (`boolean`, optional): Filter Frameworks by ready state. Example: true.
- `name` (`string`, optional): Filter Frameworks by name (partial match). Example: SOC 2.
- `size` (`integer`, optional): Number of results to return. Example: 50.
- `sort` (`string`, optional): Which field to sort by. Example: createdAt. One of: `createdAt`, `updatedAt`.
- `sortDir` (`string`, optional): The direction to sort the data. Example: ASC. One of: `ASC`, `DESC`.

Example input: `{"workspaceId":1}`

### `drata_monitoring_test_failures_list`

List Monitoring Test Failures · Read-only

List the resources that fail a Drata monitoring test.
Returns each failing resource with its status, provider, resource name and type, account, region and cause, plus the time of the last check, with a cursor for the next page.
Use this to see what needs fixing for a failing test.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `testId` (`integer`, required): The ID of the monitoring test. Get it from drata_monitoring_tests_list. Example: 1.
- `workspaceId` (`integer`, required): The ID of the Drata workspace. Get it from drata_workspaces_list. Example: 1.
- `cursor` (`string`, optional): This parameter is used to paginate through results. No value is needed for the first request. If there are additional results, the response will contain a `pagination.cursor` value that can be used in the subsequent request to retrieve the next page of results. Example: eyJpZCI6MTAwfQ==.
- `expand` (`array`, optional): List of subcollections and sub-objects to expand. Pass `tags` to include cloud-provider resource tags on each item when available. Tag resolution may add latency to the response. Tags are not present for every resource. Valid values: tags. Example: ["tags"].
- `includeExclusions` (`boolean`, optional): Include excluded Monitor Test failures in the results. Excluded findings are returned with `status` set to `EXCLUDED`; findings still failing the test are returned with `status` set to `OPEN`. Example: false.
- `includeTotalCount` (`boolean`, optional): Include total count of all matching records in response. Only honored on first page (when cursor is null). Example: false.
- `size` (`integer`, optional): Number of results to return. Example: 50.
- `sort` (`string`, optional): Which field to sort by. Example: createdAt. One of: `createdAt`, `updatedAt`.
- `sortDir` (`string`, optional): The direction to sort the data. Example: ASC. One of: `ASC`, `DESC`.

Example input: `{"testId":1,"workspaceId":1}`

### `drata_monitoring_test_get`

Get Monitoring Test · Read-only

Get one monitoring test in a Drata workspace by ID.
Returns the test's name, description, check status and result, last passed time, failing-since time and linked controls.
Use this to check a test after drata_monitoring_test_retest.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `testId` (`integer`, required): The ID of the monitoring test. Get it from drata_monitoring_tests_list. Example: 1.
- `workspaceId` (`integer`, required): The ID of the Drata workspace. Get it from drata_workspaces_list. Example: 1.
- `cursor` (`string`, optional): This parameter is used to paginate through results. No value is needed for the first request. If there are additional results, the response will contain a `pagination.cursor` value that can be used in the subsequent request to retrieve the next page of results. Example: eyJpZCI6MTAwfQ==.
- `expand` (`array`, optional): List of subcollections and sub-objects to expand. Valid values: controls, monitorInstances, disablingUser. Example: ["controls"].
- `size` (`integer`, optional): Number of results to return. Example: 50.
- `sort` (`string`, optional): Which field to sort by. Example: createdAt. One of: `createdAt`, `updatedAt`.
- `sortDir` (`string`, optional): The direction to sort the data. Example: ASC. One of: `ASC`, `DESC`.

Example input: `{"testId":1,"workspaceId":1}`

### `drata_monitoring_tests_list`

List Monitoring Tests · Read-only

List the automated monitoring tests in a Drata workspace.
Returns each test's id, name, description, check status and result, last passed time and failing-since time, with a cursor for the next page.
Use this to see which automated checks pass or fail. Use drata_monitoring_test_failures_list for the failing resources.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `workspaceId` (`integer`, required): The ID of the Drata workspace. Get it from drata_workspaces_list. Example: 1.
- `checkResultStatus` (`string`, optional): Filter Monitors by result status. Example: READY. One of: `READY`, `PASSED`, `FAILED`, `ERROR`, `PREAUDIT`.
- `checkStatus` (`string`, optional): Filter Monitors by system status. Example: UNUSED. One of: `UNUSED`, `NEW`, `ENABLED`, `DISABLED`, `TESTING`.
- `cursor` (`string`, optional): This parameter is used to paginate through results. No value is needed for the first request. If there are additional results, the response will contain a `pagination.cursor` value that can be used in the subsequent request to retrieve the next page of results. Example: eyJpZCI6MTAwfQ==.
- `draft` (`boolean`, optional): Filter Monitors by draft state: true returns only drafts, false (the default) only published tests. Example: false.
- `expand` (`array`, optional): List of subcollections and sub-objects to expand. Valid values: controls, monitorInstances, disablingUser. Example: ["controls"].
- `includeTotalCount` (`boolean`, optional): Include total count of all matching records in response. Only honored on first page (when cursor is null). Example: false.
- `name` (`string`, optional): Filter Monitors by name (prefix match, case-insensitive). Send it again with each `cursor` page. Example: MFA.
- `size` (`integer`, optional): Number of results to return. Example: 50.
- `sort` (`string`, optional): Which field to sort by. Example: createdAt. One of: `createdAt`, `updatedAt`.
- `sortDir` (`string`, optional): The direction to sort the data. Example: ASC. One of: `ASC`, `DESC`.
- `testSource` (`string`, optional): Filter monitors by test source type (DRATA for built-in tests, CUSTOM for user-created tests, ACORN for compliance-as-code tests, EXTERNAL for external tests, DRATA_LIBRARY for Drata library tests). Example: DRATA. One of: `DRATA`, `CUSTOM`, `EXTERNAL`, `ACORN`, `DRATA_LIBRARY`.
- `type` (`string`, optional): Filter Monitors by check type (associated monitor instances). Example: POLICY. One of: `POLICY`, `IN_DRATA`, `AGENT`, `INFRASTRUCTURE`, `VERSION_CONTROL`, `IDENTITY`, `TICKETING`, `HRIS`, `OBSERVABILITY`, `CUSTOM`.

Example input: `{"workspaceId":1}`

### `drata_personnel_devices_list`

List Personnel Devices · Read-only

List the devices registered to a Drata personnel record.
Returns each device's id, OS version, serial number, model, compliance flag and checks, and security settings such as screen lock, antivirus and encryption, with pagination.
Use this to check a person's device compliance.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `personnelId` (`string`, required): The personnel record ID from drata_personnel_list, or the person's email prefixed with email: (for example email:jane@example.com). Example: 123.
- `cursor` (`string`, optional): This parameter is used to paginate through results. No value is needed for the first request. If there are additional results, the response will contain a `pagination.cursor` value that can be used in the subsequent request to retrieve the next page of results. Example: eyJpZCI6MTAwfQ==.
- `expand` (`array`, optional): List of subcollections and sub-objects to expand. Valid values: asset, complianceChecks, documents, identifiers. Example: ["asset"].
- `externalId` (`string`, optional): An externally sourced unique identifier for a device. Example: example.
- `includeTotalCount` (`boolean`, optional): Include total count of all matching records in response. Only honored on first page (when cursor is null). Example: false.
- `macAddress` (`string`, optional): The device MAC address. Example: 65-F9-3D-85-7B-6B,99-A9-3E-14-7A-3E.
- `serialNumber` (`string`, optional): The device serial number. Example: NKRTSPY456.
- `size` (`integer`, optional): Number of results to return. Example: 50.
- `sort` (`string`, optional): Which field to sort by. Example: createdAt. One of: `createdAt`, `updatedAt`.
- `sortDir` (`string`, optional): The direction to sort the data. Example: ASC. One of: `ASC`, `DESC`.
- `sourceType` (`string`, optional): Device source type. Example: AGENT. One of: `AGENT`, `JAMF`, `INTUNE`, `KANDJI`, `JUMPCLOUD`, `HEXNODE_UEM`, `UNKNOWN`, `RIPPLING`, `WORKSPACE_ONE`, `KOLIDE`, `CUSTOM`, `INTUNE_GCC_HIGH`, `CUSTOM_XFA`, `NINJAONE`.

Example input: `{"personnelId":"<personnelId>"}`

### `drata_personnel_get`

Get Personnel · Read-only

Get one personnel record in Drata by ID or by email.
Returns the person's user, employment status, dates, compliance checks and any expanded sub-objects.
Use this to check one person's compliance status. Use drata_personnel_list to browse.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `personnelId` (`string`, required): The personnel record ID from drata_personnel_list, or the person's email prefixed with email: (for example email:jane@example.com). Example: 123.
- `expand` (`array`, optional): List of subcollections and sub-objects to expand. Valid values: customFields, complianceChecks, reasonProvider, user. Example: ["customFields"].

Example input: `{"personnelId":"<personnelId>"}`

### `drata_personnel_list`

List Personnel · Read-only

List personnel records in Drata, filtered by employment or compliance status.
Returns each person's id, user, employment status, start and separation dates and compliance status, with a cursor for the next page.
Use this to review onboarding and compliance status across the company. Use drata_personnel_get for one person.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `complianceStatus` (`array`, optional): Filter Personnel by overall compliance status. Valid values: MISCONFIGURED, PASS, FAIL, EXCLUDED, NOT_ASSESSED. Example: ["MISCONFIGURED"].
- `cursor` (`string`, optional): This parameter is used to paginate through results. No value is needed for the first request. If there are additional results, the response will contain a `pagination.cursor` value that can be used in the subsequent request to retrieve the next page of results. Example: eyJpZCI6MTAwfQ==.
- `employmentStatus` (`array`, optional): Personnel by employment statuses. Valid values: CURRENT_EMPLOYEE, FORMER_EMPLOYEE, CURRENT_CONTRACTOR, FORMER_CONTRACTOR, OUT_OF_SCOPE, UNKNOWN, SPECIAL_FORMER_EMPLOYEE, SPECIAL_FORMER_CONTRACTOR, FUTURE_HIRE, SERVICE_ACCOUNT. Example: ["CURRENT_EMPLOYEE"].
- `expand` (`array`, optional): List of subcollections and sub-objects to expand. Valid values: customFields, complianceChecks, reasonProvider, user. Example: ["customFields"].
- `includeTotalCount` (`boolean`, optional): Include total count of all matching records in response. Only honored on first page (when cursor is null). Example: false.
- `size` (`integer`, optional): Number of results to return. Example: 50.
- `sort` (`string`, optional): Which field to sort by. Example: createdAt. One of: `createdAt`, `updatedAt`.
- `sortDir` (`string`, optional): The direction to sort the data. Example: ASC. One of: `ASC`, `DESC`.

Example input: `{}`

### `drata_policies_list`

List Policies · Read-only

List the policies in Drata.
Returns each policy's id, name, description, owner, status and current version, with a cursor for the next page.
Use this to review policy status. Use drata_policy_get for one policy.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `cursor` (`string`, optional): This parameter is used to paginate through results. No value is needed for the first request. If there are additional results, the response will contain a `pagination.cursor` value that can be used in the subsequent request to retrieve the next page of results. Example: eyJpZCI6MTAwfQ==.
- `expand` (`array`, optional): List of subcollections and sub-objects to expand. Valid values: groups, weekTimeFrameSlas, gracePeriodSlas, p3MatrixSlas, owner. Example: ["groups"].
- `includeTotalCount` (`boolean`, optional): Include total count of all matching records in response. Only honored on first page (when cursor is null). Example: false.
- `name` (`string`, optional): Filter Policies by name (partial match). Example: Data Protection Policy.
- `reviewerStatus` (`array`, optional): Filter Policies by the reviewer's review status on an active approval. Typically used with reviewerUserId. Valid values: READY_FOR_REVIEW, APPROVED, CHANGES_REQUESTED, DEADLINE_EXCEEDED. Example: ["READY_FOR_REVIEW"].
- `reviewerUserId` (`string`, optional): Filter Policies by a reviewer. A Drata integer ID, an email address of the form 'email:value', or 'me' to reference the authenticated user. Note: 'me' is only available when authenticating with OAuth 2.1 Authorization Code grant, not with Public API Keys. Example: me.
- `size` (`integer`, optional): Number of results to return. Example: 50.
- `sort` (`string`, optional): Which field to sort by. Example: createdAt. One of: `createdAt`, `updatedAt`.
- `sortDir` (`string`, optional): The direction to sort the data. Example: ASC. One of: `ASC`, `DESC`.
- `statuses` (`array`, optional): Filter Policies by one or more statuses. Valid values: ACTIVE, ARCHIVED, REPLACED, UNACCEPTABLE, OUTDATED. Example: ["ACTIVE"].

Example input: `{}`

### `drata_policy_get`

Get Policy · Read-only

Get one Drata policy by ID.
Returns the policy's name, description, scope, owner, status, current version, renewal date and publish and approval dates.
Use this when you have a policy ID. Use drata_policies_list to find one.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `policyId` (`integer`, required): The ID of the policy. Get it from drata_policies_list. Example: 301.
- `expand` (`array`, optional): List of subcollections and sub-objects to expand. Valid values: groups, controls, weekTimeFrameSlas, gracePeriodSlas, p3MatrixSlas, owner. Example: ["groups"].

Example input: `{"policyId":301}`

### `drata_risks_search`

Search Risks · Read-only

Search risks across every Drata risk register by text, status, treatment plan, type, score, dates, owners or linked controls.
Returns matching risks with their scores, treatment plan, owners and status, with a cursor for the next page.
Use this to find risks. Expand owners, controls or notes to include them.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `anticipatedCompletionDateGte` (`string`, optional): Filter Risks with anticipated completion date on or after this ISO 8601 timestamp. Example: 2026-01-15.
- `anticipatedCompletionDateLte` (`string`, optional): Filter Risks with anticipated completion date on or before this ISO 8601 timestamp. Example: 2026-01-15.
- `categories` (`array`, optional): Filter Risks by exact category name membership. Example: ["example"].
- `completedDateGte` (`string`, optional): Filter Risks with actual completion date on or after this ISO 8601 timestamp. Example: 2026-01-15.
- `completedDateLte` (`string`, optional): Filter Risks with actual completion date on or before this ISO 8601 timestamp. Example: 2026-01-15.
- `controls` (`array`, optional): Filter Risks by exact control code membership (e.g. `AC-04`). Example: ["example"].
- `cursor` (`string`, optional): This parameter is used to paginate through results. No value is needed for the first request. If there are additional results, the response will contain a `pagination.cursor` value that can be used in the subsequent request to retrieve the next page of results. Example: eyJpZCI6MTAwfQ==.
- `expand` (`array`, optional): List of subcollections and sub-objects to expand. Valid values: owners, reviewers, controls, categories, documents, notes, tickets, tasks, customFields. Example: ["owners"].
- `facets` (`array`, optional): Filter dimensions for which to return value counts in the response. Only honored on the first page (when `cursor` is null). Each requested facet adds one terms aggregation to the search query. Bounded enum facets (`status`, `treatmentPlan`, `type`) are enriched with zero-count entries; unbounded facets (`categories`, `controls`, `ownerEmails`, `reviewerEmails`, `vendorNames`, `riskRegisterId`) return only values present in the result set. Valid values: status, treatmentPlan, type, categories, controls, ownerEmails, reviewerEmails, vendorNames, riskRegisterId. Example: ["status"].
- `includeTotalCount` (`boolean`, optional): Include total count of all matching records in response. Only honored on first page (when cursor is null). Example: false.
- `inherentScoreGte` (`number`, optional): Filter Risks by minimum inherent (pre-mitigation) score (inclusive). Example: 10.
- `inherentScoreLte` (`number`, optional): Filter Risks by maximum inherent (pre-mitigation) score (inclusive). Example: 10.
- `ownerEmails` (`array`, optional): Filter Risks by owner email membership. Example: ["example"].
- `q` (`string`, optional): Free-text search across `title`, `description`, `riskId`, and `vendorName`. Fuzzy, prefix-aware, and relevance-ranked. Example: unauthorized access.
- `residualScoreGte` (`number`, optional): Filter Risks by minimum residual (post-mitigation) score (inclusive). Example: 10.
- `residualScoreLte` (`number`, optional): Filter Risks by maximum residual (post-mitigation) score (inclusive). Example: 10.
- `reviewerEmails` (`array`, optional): Filter Risks by reviewer email membership. Example: ["example"].
- `riskRegisterId` (`array`, optional): Narrow results to Risks in this subset of Risk Registers. Each ID must be a Risk Register the caller can access; unknown or inaccessible IDs are silently filtered out. Omit to search every Risk Register accessible to the caller. Example: [1, 2].
- `size` (`integer`, optional): Number of results to return. Example: 50.
- `sort` (`string`, optional): Which field to sort by. Highest residual risk first (with `sortDir=DESC`, the default) is the natural default view for a risk register. Example: residualScore. One of: `residualScore`, `inherentScore`, `anticipatedCompletionDate`, `completedDate`, `title`, `riskId`, `status`, `vendorName`, `createdAt`, `updatedAt`.
- `sortDir` (`string`, optional): The direction to sort the data. Example: ASC. One of: `ASC`, `DESC`.
- `status` (`array`, optional): Filter Risks by one or more workflow statuses. Valid values: ACTIVE, ARCHIVED, CLOSED. Example: ["ACTIVE"].
- `treatmentPlan` (`array`, optional): Filter Risks by treatment plan. Valid values: UNTREATED, ACCEPT, TRANSFER, AVOID, MITIGATE. Example: ["UNTREATED"].
- `type` (`array`, optional): Filter Risks by version type. Valid values: INTERNAL, EXTERNAL. Example: ["INTERNAL"].
- `vendorNames` (`array`, optional): Filter Risks by exact vendor name membership. Each Risk is indexed with a single vendor name (the first associated vendor), so a Risk matches if that vendor name is in the supplied list. Example: ["example"].

Example input: `{}`

### `drata_tasks_list`

List Tasks · Read-only

List the custom tasks in a Drata workspace.
Returns each task's id, title, description, type, assignee, due date and completion status, with pagination.
Use this to review open compliance tasks. Use drata_task_create to add one.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `workspaceId` (`integer`, required): The ID of the Drata workspace. Get it from drata_workspaces_list. Example: 1.
- `assigneeId` (`integer`, optional): Filter by assigned User ID. Example: 456.
- `controlId` (`integer`, optional): The ID of the control. Get it from drata_controls_list. Example: 101.
- `createdById` (`integer`, optional): Filter by User ID who created the task. Example: 123.
- `cursor` (`string`, optional): This parameter is used to paginate through results. No value is needed for the first request. If there are additional results, the response will contain a `pagination.cursor` value that can be used in the subsequent request to retrieve the next page of results. Example: eyJpZCI6MTAwfQ==.
- `description` (`string`, optional): Filter by Task description (prefix search). Example: quarterly review.
- `dueDateFrom` (`string`, optional): Filter Tasks with due date on or after this value (inclusive). Example: 2020-07-06.
- `dueDateTo` (`string`, optional): Filter Tasks with due date on or before this value (inclusive). Example: 2020-07-06.
- `expand` (`array`, optional): List of subcollections and sub-objects to expand. Valid values: assignee, createdBy, controls, risks, policies, schedule. Example: ["assignee"].
- `includeTotalCount` (`boolean`, optional): Include total count of all matching records in response. Only honored on first page (when cursor is null). Example: false.
- `size` (`integer`, optional): Number of results to return. Example: 50.
- `sort` (`string`, optional): Which field to sort by. Example: createdAt. One of: `createdAt`, `updatedAt`, `dueDate`.
- `sortDir` (`string`, optional): The direction to sort the data. Example: ASC. One of: `ASC`, `DESC`.
- `status` (`string`, optional): Filter by Task status. Example: PAST_DUE. One of: `PAST_DUE`, `COMPLETED`, `INCOMPLETE`.
- `taskType` (`string`, optional): Filter by Task type. Example: POLICY_RENEWALS. One of: `POLICY_RENEWALS`, `EVIDENCE`, `VENDOR`, `EXTERNAL_EVIDENCE`, `REPORT`, `GENERAL`, `CONTROL`, `RISK`, `CONTROL_APPROVALS`, `POLICY_APPROVALS`.
- `title` (`string`, optional): Filter by Task title (prefix search). Example: Review SOC 2.

Example input: `{"workspaceId":1}`

### `drata_user_get`

Get User · Read-only

Get one Drata user by ID.
Returns the user's email, name, job title and roles, plus background checks, documents or identities when expanded.
Use this when you have a user ID. Use drata_users_list to find one.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `userId` (`string`, required): The Drata user ID. Get it from drata_users_list. Example: 456.
- `expand` (`array`, optional): List of subcollections and sub-objects to expand. Valid values: backgroundChecks, documents, personnel, identities, roles. Example: ["backgroundChecks"].

Example input: `{"userId":"<userId>"}`

### `drata_users_list`

List Users · Read-only

List users in the Drata account, optionally filtered by first or last name.
Returns each user's id, email, name, job title and roles, with a cursor for the next page.
Use this to find a user ID for owners and assignees. Use drata_user_get for one user.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `cursor` (`string`, optional): This parameter is used to paginate through results. No value is needed for the first request. If there are additional results, the response will contain a `pagination.cursor` value that can be used in the subsequent request to retrieve the next page of results. Example: eyJpZCI6MTAwfQ==.
- `expand` (`array`, optional): List of subcollections and sub-objects to expand. Valid values: backgroundChecks, documents, personnel, identities, roles. Example: ["backgroundChecks"].
- `firstName` (`string`, optional): Filter users whose first name starts with the provided value (prefix match). For example, `firstName=John` matches users named John, Johnathan, Johnny, etc. Example: John.
- `includeTotalCount` (`boolean`, optional): Include total count of all matching records in response. Only honored on first page (when cursor is null). Example: false.
- `lastName` (`string`, optional): Filter users whose last name starts with the provided value (prefix match). For example, `lastName=Sm` matches users named Smith, Smithson, etc. Example: Doe.
- `size` (`integer`, optional): Number of results to return. Example: 50.
- `sort` (`string`, optional): Which field to sort by. Example: createdAt. One of: `createdAt`, `updatedAt`.
- `sortDir` (`string`, optional): The direction to sort the data. Example: ASC. One of: `ASC`, `DESC`.

Example input: `{}`

### `drata_vendor_get`

Get Vendor · Read-only

Get one vendor in Drata by ID. Needs a Drata TPRM plan.
Returns the vendor's category, risk, type, status, URLs, services provided, data stored, PII flag, password policy and contacts.
Use this when you have a vendor ID. Use drata_vendors_list to find one.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `vendorId` (`integer`, required): The ID of the vendor. Get it from drata_vendors_list. Example: 55.
- `expand` (`array`, optional): List of subcollections and sub-objects to expand. Valid values: customFields, documents, integrations, lastQuestionnaire, latestSecurityReviews, reviews, vendorUser, vendorRelationshipContact, dataAccessedOrProcessed, scheduleConfiguration, customVendorType, inherentRiskLevel, residualRiskLevel. Example: ["customFields"].

Example input: `{"vendorId":55}`

### `drata_vendors_list`

List Vendors · Read-only

List the third-party vendors tracked in Drata, filtered by category, risk, status, type or renewal. Needs a Drata TPRM plan.
Returns each vendor's id, name, category, risk, type, status and critical flag, with a cursor for the next page.
Use this to review vendor risk. Use drata_vendor_get for one vendor.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `actionRequired` (`boolean`, optional): Filter to "action required" vendors: current (not prospective/archived), with a directory entry and an owner email, whose renewal is due soon or overdue. Example: true.
- `categories` (`array`, optional): Filter to Vendors in any of these categories (business unit). Multi-select is OR. Valid values: ENGINEERING, PRODUCT, MARKETING, CS, SALES, FINANCE, HR, ADMINISTRATIVE, SECURITY, LEGAL, INFORMATION_TECHNOLOGY, NONE. Example: ["ENGINEERING"].
- `category` (`string`, optional): The category of the Vendors. Example: ENGINEERING. One of: `ENGINEERING`, `PRODUCT`, `MARKETING`, `CS`, `SALES`, `FINANCE`, `HR`, `ADMINISTRATIVE`, `SECURITY`, `LEGAL`, `INFORMATION_TECHNOLOGY`, `NONE`.
- `cursor` (`string`, optional): This parameter is used to paginate through results. No value is needed for the first request. If there are additional results, the response will contain a `pagination.cursor` value that can be used in the subsequent request to retrieve the next page of results. Example: eyJpZCI6MTAwfQ==.
- `expand` (`array`, optional): List of subcollections and sub-objects to expand. Valid values: customFields, documents, integrations, lastQuestionnaire, latestSecurityReviews, reviews, vendorUser, vendorRelationshipContact, dataAccessedOrProcessed, scheduleConfiguration, customVendorType, inherentRiskLevel, residualRiskLevel. Example: ["customFields"].
- `impactLevel` (`string`, optional): Overall Vendor impact level. Example: INSIGNIFICANT. One of: `INSIGNIFICANT`, `MINOR`, `MODERATE`, `MAJOR`, `CRITICAL`, `UNSCORED`.
- `includeTotalCount` (`boolean`, optional): Include total count of all matching records in response. Only honored on first page (when cursor is null). Example: false.
- `isSubProcessor` (`boolean`, optional): Filter to sub-processor vendors (true) or non-sub-processors (false). Example: true.
- `nextReviewDeadlineStatus` (`array`, optional): Filter by next-review-deadline status: NO_RENEWAL / DUE_SOON / OVERDUE (multi-select is OR). Valid values: NO_RENEWAL, DUE_SOON, OVERDUE. Example: ["NO_RENEWAL"].
- `renewalDate` (`string`, optional): Vendor renewal date (date-only YYYY-MM-DD, matched exactly). Example: 2020-07-06.
- `renewalScheduleType` (`string`, optional): Vendor renewal schedule type. Example: ONE_MONTH. One of: `ONE_MONTH`, `TWO_MONTHS`, `THREE_MONTHS`, `SIX_MONTHS`, `ONE_YEAR`, `CUSTOM`, `NONE`.
- `risk` (`string`, optional): Filter data to Vendors of this risk level. Example: NONE. One of: `NONE`, `LOW`, `MODERATE`, `HIGH`.
- `size` (`integer`, optional): Number of results to return. Example: 50.
- `sort` (`string`, optional): Which field to sort by. Example: createdAt. One of: `createdAt`, `updatedAt`.
- `sortDir` (`string`, optional): The direction to sort the data. Example: ASC. One of: `ASC`, `DESC`.
- `status` (`string`, optional): The status of the Vendors. Example: PROSPECTIVE. One of: `PROSPECTIVE`, `ACTIVE`, `ARCHIVED`, `APPROVED`, `REJECTED`, `FLAGGED`, `ON_HOLD`, `OFFBOARDED`, `UNDER_REVIEW`, `NONE`.
- `statuses` (`array`, optional): Filter to Vendors in any of these statuses (multi-select is OR). `NONE` matches Vendors with no status set. `CURRENT` matches the current Vendor book: every Vendor that is not PROSPECTIVE or ARCHIVED, including those with no status. Valid values: PROSPECTIVE, ACTIVE, ARCHIVED, APPROVED, REJECTED, FLAGGED, ON_HOLD, OFFBOARDED, UNDER_REVIEW, NONE, CURRENT. Example: ["PROSPECTIVE"].
- `type` (`string`, optional): Vendor type. Example: VENDOR. One of: `VENDOR`, `SUPPLIER`, `CONTRACTOR`, `PARTNER`, `OTHER`, `NONE`.
- `types` (`array`, optional): Filter to Vendors of any of these types (multi-select is OR). Valid values: VENDOR, SUPPLIER, CONTRACTOR, PARTNER, OTHER, NONE. Example: ["VENDOR"].
- `vendorTypeIds` (`array`, optional): Filter to Vendors of any of these vendor-type ids (the tenant-defined vendor-type taxonomy from vendor settings; resolve names via GET /vendor-types). Multi-select is OR. Example: [1, 2].
- `vendorUserIds` (`array`, optional): Filter to Vendors whose security owner is one of these user IDs. Mirrors the security-owner filter in the app. Example: [1, 2, 3].

Example input: `{}`

### `drata_workspaces_list`

List Workspaces · Read-only

List the workspaces in the Drata account.
Returns each workspace's id, name, description and primary flag, with pagination.
Use this first: most control, evidence, test, framework and task tools need a workspace ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `cursor` (`string`, optional): This parameter is used to paginate through results. No value is needed for the first request. If there are additional results, the response will contain a `pagination.cursor` value that can be used in the subsequent request to retrieve the next page of results. Example: eyJpZCI6MTAwfQ==.
- `expand` (`array`, optional): List of subcollections and sub-objects to expand. Valid values: frameworks, personnelScope. Example: ["frameworks"].
- `includeTotalCount` (`boolean`, optional): Include total count of all matching records in response. Only honored on first page (when cursor is null). Example: false.
- `size` (`integer`, optional): Number of results to return. Example: 50.
- `sort` (`string`, optional): Which field to sort by. Example: createdAt. One of: `createdAt`, `updatedAt`.
- `sortDir` (`string`, optional): The direction to sort the data. Example: ASC. One of: `ASC`, `DESC`.

Example input: `{}`

### `drata_monitoring_test_retest`

Run Monitoring Test · Write

Run a Drata monitoring test now instead of waiting for its schedule. The run is asynchronous: success means the run was accepted, not that the test passed.
Returns the test ID and its check status.
Use this after fixing a failure, then poll drata_monitoring_test_get for the result.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `testId` (`integer`, required): The ID of the monitoring test. Get it from drata_monitoring_tests_list. Example: 1.
- `workspaceId` (`integer`, required): The ID of the Drata workspace. Get it from drata_workspaces_list. Example: 1.

Example input: `{"testId":1,"workspaceId":1}`

### `drata_personnel_update`

Update Personnel · Write

Update a Drata personnel record's start or separation date, employment status or custom fields. Fields you set manually stop syncing from your identity provider or HRIS.
Returns the updated personnel record.
Use this to correct HR data in Drata. Use drata_personnel_get to read the record first.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `personnelId` (`string`, required): The personnel record ID from drata_personnel_list, or the person's email prefixed with email: (for example email:jane@example.com). Example: 123.
- `customFields` (`array`, optional): Custom Fields for the Person. Requires your account have the Custom Fields and Formulas feature. Contact your Account Manager for help upgrading. Example: [{"id": 1, "name": "Compliance Status", "value": "Security & IT"}].
- `employmentStatus` (`string`, optional): The desired employment status to be updated. Example: CURRENT_CONTRACTOR. One of: `CURRENT_EMPLOYEE`, `FORMER_EMPLOYEE`, `CURRENT_CONTRACTOR`, `FORMER_CONTRACTOR`, `OUT_OF_SCOPE`, `UNKNOWN`, `SPECIAL_FORMER_EMPLOYEE`, `SPECIAL_FORMER_CONTRACTOR`, `FUTURE_HIRE`, `SERVICE_ACCOUNT`.
- `notHumanReason` (`string`, optional): Explains why the employment status of this personnel is marked as `OUT_OF_SCOPE`. This field is required if the `employmentStatus` is set to `OUT_OF_SCOPE`. Example: This is not a real personnel, but a placeholder for anyone in charge of X.
- `separatedAt` (`string`, optional): The date when this person was separated from the company system. Example: 2020-07-06.
- `startedAt` (`string`, optional): The date when this person started working at the company. Note: Once manually set, automatic updates from identity providers (IDP) and HRIS systems will be ignored. Use the resync endpoint to restore automatic updates. Example: 2020-07-06.

Example input: `{"personnelId":"<personnelId>"}`

### `drata_task_create`

Create Task · Write

Create a custom task in a Drata workspace, optionally linked to controls, risks or policies.
Returns the created task.
Use this to assign compliance follow-up work. Provide a title unless you pass configurationId for a recurring task's occurrence.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `dueDate` (`string`, required): Due date. With `configurationId` this selects the occurrence to create and must be a date that recurring Task actually falls on. Example: 2020-07-06.
- `workspaceId` (`integer`, required): The ID of the Drata workspace. Get it from drata_workspaces_list. Example: 1.
- `assigneeId` (`integer`, optional): ID of the User to assign the task to. Example: 456.
- `configurationId` (`integer`, optional): Create this Task from an occurrence of a recurring Task, as returned by `configurationId` on Upcoming Tasks. `dueDate` then selects which occurrence, and every other property is taken from the recurring Task, so none may be sent. This is a short-lived handle rather than a durable identifier: it is replaced whenever the recurring Task is edited, so list Upcoming Tasks and create from the value in that response rather than caching it. Example: 42.
- `controlIds` (`array`, optional): IDs of Controls to link to this Task. Can be combined with `riskIds` and `policyIds`. Example: [101, 102].
- `description` (`string`, optional): Task description. Example: Quarterly review of access control policies.
- `policyIds` (`array`, optional): IDs of Policies to link to this Task. Can be combined with `controlIds` and `riskIds`. Example: [301, 302].
- `riskIds` (`array`, optional): IDs of Risks to link to this Task. Can be combined with `controlIds` and `policyIds`. Example: [201].
- `taskType` (`string`, optional): Task type. Example: GENERAL. One of: `POLICY_RENEWALS`, `EVIDENCE`, `VENDOR`, `EXTERNAL_EVIDENCE`, `REPORT`, `GENERAL`, `CONTROL`, `RISK`, `CONTROL_APPROVALS`, `POLICY_APPROVALS`.
- `title` (`string`, optional): Task title. Required unless `configurationId` is supplied. Example: Review access controls.

Example input: `{"dueDate":"<dueDate>","workspaceId":1}`

### `drata_vendor_create`

Create Vendor · Write

Add a third-party vendor to Drata. Needs a Drata TPRM plan.
Returns the created vendor.
Use this to start tracking a new vendor. Use drata_vendors_list to check it is not already there.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): The name of the Vendor. Example: Acme.
- `accountId` (`string`, optional): Account Id. Example: 36.
- `category` (`string`, optional): The type of Vendor. Example: ENGINEERING. One of: `ENGINEERING`, `PRODUCT`, `MARKETING`, `CS`, `SALES`, `FINANCE`, `HR`, `ADMINISTRATIVE`, `SECURITY`, `LEGAL`, `INFORMATION_TECHNOLOGY`, `NONE`.
- `confirmed` (`boolean`, optional): Indicate if all Vendor data is confirmed. Example: true.
- `contactAtVendor` (`string`, optional): Name of the corresponding account manager for this Vendor. Example: John Doe.
- `contactEmail` (`string`, optional): Semicolon-separated list of vendor contact email addresses. Example: jdoe@company.com;jane@company.com.
- `cost` (`string`, optional): Annual Contract Value for the Vendor in Cents unit. Example: 1088.
- `critical` (`boolean`, optional): Indicates if the Vendor is considered critical. Example: false.
- `customFields` (`array`, optional): Custom Fields for the Vendor. Requires your account have the Custom Fields and Formulas feature. Contact your Account Manager for help upgrading. Example: [{"id": 1, "name": "Compliance Status", "value": "Security & IT"}].
- `dataAccessedOrProcessedList` (`array`, optional): List of data accessed or processed enum type. Valid values: GENERAL, PUBLIC, CONTROLLED_UNCLASSIFIED, FINANCIAL, PROPRIETARY, EMPLOYEE_PERSONNEL, PERSONAL_IDENTIFIABLE_INFORMATION, PROTECTED_HEALTH_INFORMATION, OTHER_PERSONAL_OR_SENSITIVE, CARDHOLDER_DATA. Example: ["FINANCIAL", "GENERAL"].
- `dataStored` (`string`, optional): Description of the type of data the Vendor stores. Example: resulting reports of security scans.
- `environmentAccess` (`string`, optional): Vendor environment access privileges. Example: READ_ONLY. One of: `NO`, `READ_ONLY`, `READ_WRITE`.
- `hasPii` (`boolean`, optional): Indicates whether this Vendor stores any type of Personally Identifiable Information (PII). Example: true.
- `impactLevel` (`string`, optional): Vendor overall impact level. Example: INSIGNIFICANT. One of: `INSIGNIFICANT`, `MINOR`, `MODERATE`, `MAJOR`, `CRITICAL`, `UNSCORED`.
- `inherentRiskLevelId` (`integer`, optional): Custom inherent risk level ID. Only honored when custom vendor risk levels are enabled. Example: 1.
- `integrations` (`array`, optional): List of vendor IDs. Example: [1, 2, 3].
- `isSubProcessor` (`boolean`, optional): Indicates whether this Vendor is considered a subprocessor. Example: false.
- `isSubProcessorActive` (`boolean`, optional): [Deprecated] Indicates whether this subprocessor is active. Example: false.
- `location` (`string`, optional): Location where the Vendor services are provided. Example: San Diego.
- `notes` (`string`, optional): Additional notes for Vendor. Example: Meeting once a month to adjust contract.
- `operationalImpact` (`string`, optional): Vendor level of operational impact. Example: IMPORTANT. One of: `NONE`, `LOW`, `NORMAL`, `IMPORTANT`, `CRITICAL`.
- `passwordMfaEnabled` (`boolean`, optional): Indicates whether multi-factor authentication is enabled for this Vendor. Example: true.
- `passwordMinLength` (`number`, optional): Minimum character length required for a password. Example: 8.
- `passwordPolicy` (`string`, optional): The Vendor password policy. Example: USERNAME_PASSWORD. One of: `USERNAME_PASSWORD`, `SSO`, `LDAP`, `NONE`, `NOT_APPLICABLE`, `SCIM`, `OTHER`.
- `passwordRequiresMinLength` (`boolean`, optional): Indicates whether there is a minimum length requirement for password. Example: true.
- `passwordRequiresNumber` (`boolean`, optional): Indicates whether a password requires numbers. Example: true.
- `passwordRequiresSymbol` (`boolean`, optional): Indicates whether a password requires non-alpha-numeric characters. Example: true.
- `privacyUrl` (`string`, optional): Vendor Privacy Policy URL. Example: https://acme.com/privacy.
- `renewalDate` (`string`, optional): Vendor renewal date. Example: 2025-07-01T16:45:55.246Z.
- `renewalScheduleType` (`string`, optional): Vendor renewal schedule type. Example: ONE_YEAR. One of: `ONE_MONTH`, `TWO_MONTHS`, `THREE_MONTHS`, `SIX_MONTHS`, `ONE_YEAR`, `CUSTOM`, `NONE`.
- `residualRiskLevelId` (`integer`, optional): Custom residual risk level ID. Only honored when custom vendor risk levels are enabled. Example: 1.
- `risk` (`string`, optional): The level of risk associated with customer data. Example: MODERATE. One of: `NONE`, `LOW`, `MODERATE`, `HIGH`.
- `servicesProvided` (`string`, optional): Description of the services provided by the Vendor. Example: Perform security scans once a month.
- `status` (`string`, optional): The status of Vendor. Example: UNDER_REVIEW. One of: `PROSPECTIVE`, `ACTIVE`, `ARCHIVED`, `APPROVED`, `REJECTED`, `FLAGGED`, `ON_HOLD`, `OFFBOARDED`, `UNDER_REVIEW`, `NONE`.
- `termsUrl` (`string`, optional): Vendor Terms of Use URL. Example: https://acme.com/terms.
- `trustCenterUrl` (`string`, optional): Vendor Trust Center URL. Example: https://trust.example.com.
- `type` (`string`, optional): Vendor type identifier. Example: VENDOR. One of: `VENDOR`, `SUPPLIER`, `CONTRACTOR`, `PARTNER`, `OTHER`, `NONE`.
- `url` (`string`, optional): Vendor URL. Example: https://acme.com.
- `userId` (`integer`, optional): The Drata user ID. Get it from drata_users_list. Example: 456.
- `vendorRelationshipContact` (`object`, optional): The Vendor relationship contact. Pass `null` to leave it unset (no contact will be assigned). Example: {"userId": 1}.

Example input: `{"name":"<name>"}`

## Related

Other Monitoring connectors ([all 48](/agentkit/connectors/?category=monitoring)):

- [Datadog](/agentkit/connectors/datadog/): Scalekit connector, API key, 105 tools
- [1Password](/agentkit/connectors/onepassword/): Scalekit connector, Access token, 4 tools
- [Malwarebytes](/agentkit/connectors/malwarebytes/): Scalekit connector, Service account, 74 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
