# Cortex XDR MCP connector

Connect Cortex XDR to Elaichi and your analysts can review alerts, check response actions and track affected software from Claude, ChatGPT, Cursor or Microsoft Copilot, each acting as themselves, with every call logged.

Source: https://elaichi.ai/connectors/cortexxdr/

## Facts

| | |
| --- | --- |
| Application | Cortex XDR |
| Category | Security |
| AI tools | 443 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Cortex XDR is connected

- Summarize the high severity Cortex XDR alerts from the last 24 hours
- Which affected software shows up most across open alerts?
- Has the file retrieval action on the finance laptop finished?

## Connect Cortex XDR in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Cortex XDR.
2. Optionally set Share with, then press Connect.
3. Paste a Cortex XDR API key. One person generates a token in Cortex XDR and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Cortex XDR tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Cortex XDR MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Cortex XDR MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Cortex XDR MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Cortex XDR MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Cortex XDR MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Cortex XDR to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Cortex XDR tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Cortex XDR through Elaichi

### Triage the overnight alert queue

Security operations. Ask for the Cortex XDR alerts that arrived since the last shift, grouped by severity and host, and update their status as you work through them.

### Check whether a response action finished

Incident response. Find out if the file retrieval you kicked off on a laptop has completed, and pull the details of what came back, without opening the console.

### Pull the events behind an alert

Threat hunting. Get the full event chain and the packet capture tied to a suspicious alert so you can follow what the process actually did.

### See which software is affected

Vulnerability management. List the affected software Cortex XDR knows about and ask which packages show up most across open alerts before you plan patching.

### Keep the application inventory current

Application security. Add, update or import the applications your appsec program tracks in Cortex XDR, and review which assets can still be attached to each one.

### Audit who holds an API key

IT. List the Cortex XDR API keys in use, see which ones are stale, and retire the ones nobody should still have.

## Elaichi vs Zapier MCP vs Composio for Cortex XDR

All three can connect Cortex XDR to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Cortex XDR tools | Allow or restrict single Cortex XDR tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Cortex XDR call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Cortex XDR to Claude?

Connect Cortex XDR in Elaichi first: you paste the API key from your Cortex XDR tenant, and that is the whole sign-in step, with no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi, and from then on it can reach Cortex XDR as you.

### Does Cortex XDR work with ChatGPT and Cursor as well as Claude?

Yes. Once Cortex XDR is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Cortex XDR once and every client picks it up.

### What can an AI agent actually do with my Cortex XDR data?

It can list and summarize Cortex XDR alerts, update their status, pull the events and packet capture behind one, and check whether a response action such as a file retrieval has finished. It can also list affected software, manage the applications and assets in your appsec inventory, and review API keys. Short, concrete asks such as 'show me critical alerts from today' work better than long paragraphs.

### Does connecting Cortex XDR give the AI access to my whole tenant?

No. Every call to Cortex XDR runs with the role and permissions of the person who signed in, so an agent sees exactly the alerts and settings that person could see in the console. Elaichi can narrow that access further with restrictions, and it can never widen it.

### Can my team share one Cortex XDR connection?

Yes. One person connects Cortex XDR in Elaichi and shares it with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind every Cortex XDR call.

### Can I stop an agent from deleting or changing things in Cortex XDR?

Yes. Restrictions in Elaichi work per action, so you can let a role read Cortex XDR alerts but stop it from updating them, deleting API keys or changing applications, and you can set the same for one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Cortex XDR connection when someone leaves?

Offboarding that person in Elaichi ends their access to Cortex XDR at once, in every client they used. A shared Cortex XDR connection keeps working for everyone else on the team. If you ever want it gone entirely, disconnecting Cortex XDR once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

### Does the Cortex XDR MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Cortex XDR is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Cortex XDR?

Yes. Both let Claude, ChatGPT or Cursor use Cortex XDR. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Cortex XDR call.

### How is Elaichi different from Composio for Cortex XDR?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Cortex XDR: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 443 Cortex XDR tools

Every tool below is callable through https://api.elaichi.ai/mcp once Cortex XDR is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Cortex XDR abioc override** (Action). Override analytics rule severities. Create a severity override for one or more severity variations of an analytics (ABIOC) detection rule. An analytics rule can raise alerts at more than one severity. Each distinct severity path through the rule is a severity variation, identified by its own variation ID. This endpoint sets an explicit severity for the variations you list, replacing the severity defined by the rule content. [Cortex XDR API – Analytics Rules (ABIOCs): POST /public_api/v1/abioc/override]
- **Cortex XDR actions file retrieval details** (Action). File Retrieval Details. View the API required to call in order to download the file retrieved by the Retrieve File API request according to the action ID. The response contains a file hash you need to download and then unzip to view: 1. Download the file. 2. Unzip the file: unzip /tmp/file.zip Required license: Cortex XDR. [Cortex XDR API – Response Action: POST /public_api/v1/actions/file_retrieval_details]
- **Cortex XDR actions get action status** (Get). Get Action Status. Retrieve the status of the requested actions according to the action ID. Required license: Cortex XDR. [Cortex XDR API – Response Action: POST /public_api/v1/actions/get_action_status]
- **List all Cortex XDR affected software** (List). Get affected software. Get a filtered list of the software affected by one or more vulnerabilities. Required license: Requires the Cortex Cloud Posture Management add-on. [Cortex XDR API – Affected Software: POST /public_api/uvem/v1/get_affected_software]
- **Cortex XDR alerts get alerts multi events** (Get). Get Alerts Multi-Events v1. Note: This endpoint is legacy. Use the Get Alerts Multi-Events v2 endpoint. Get a list of alerts with multiple events. - Response is concatenated using AND condition (OR is not supported). - Maximum result set size is 100. - Offset is the zero-based number of alerts from the start of the result set. Cortex XDR displays in the APIs response whether an PAN NGFW type alert contains a PCAP triggering packet. [Cortex XDR 3.x REST API – Incident Management: POST /public_api/v1/alerts/get_alerts_multi_events] Available on Cortex XDR 3.x tenants (replaced by Cases / Issues on Cortex XDR 6.0 platform tenants).
- **Cortex XDR alerts get alerts multi events v 2** (Get). Get Alerts Multi-Events v2. Get a list of alerts with multiple events. - The response is concatenated using AND condition (OR is not supported). - The maximum result set size is 100. - Offset is the zero-based number of alerts from the start of the result set. Cortex XDR displays in the API response whether a PAN NGFW type alert contains a PCAP triggering packet. Use the Retrieve PCAP Packet API to retrieve a list of alert IDs and their associated PCAP data. [Cortex XDR 3.x REST API – Incident Management: POST /public_api/v2/alerts/get_alerts_multi_events] Available on Cortex XDR 3.x tenants (replaced by Cases / Issues on Cortex XDR 6.0 platform tenants).
- **Cortex XDR alerts get alerts pcap** (Get). Retrieve PCAP Packet. Retrieve a list of alert IDs and the associated PCAP triggering packets of PAN NGFW type alerts returned when running the Get Alerts and Get Extra Incident Data APIs. Maximum result set size is 100. Required license: Cortex XDR Prevent, Cortex XDR Pro per Endpoint, or Cortex XDR Pro per GB [Cortex XDR 3.x REST API – Incident Management: POST /public_api/v1/alerts/get_alerts_pcap] Available on Cortex XDR 3.x tenants (replaced by Cases / Issues on Cortex XDR 6.0 platform tenants).
- **Cortex XDR alerts insert cef alerts** (Action). Insert CEF Alerts. Upload alerts in CEF format from external alert sources. After you map CEF alert fields to Cortex XDR fields, Cortex XDR displays the alerts in related incidents and views. You can send 600 alerts per minute. Required license: Cortex XDR Pro per GB [Cortex XDR 3.x REST API – Incident Management: POST /public_api/v1/alerts/insert_cef_alerts] Available on Cortex XDR 3.x tenants (replaced by Cases / Issues on Cortex XDR 6.0 platform tenants).
- **Cortex XDR alerts insert parsed alerts** (Action). Insert Parsed Alerts. Upload alerts from external alert sources in Cortex XDR format. Cortex XDRdisplays alerts that are parsed successfully in related incidents and views. You can send 600 alerts per minute. Each request can contain a maximum of 60 alerts. Required license: Cortex XDR Pro per Endpoint or Cortex XDR Pro per GB [Cortex XDR 3.x REST API – Incident Management: POST /public_api/v1/alerts/insert_parsed_alerts] Available on Cortex XDR 3.x tenants (replaced by Cases / Issues on Cortex XDR 6.0 platform tenants).
- **List all Cortex XDR alerts** (List). Get all Alerts. Get a list of all or filtered alerts. The alerts listed are what remains after alert exclusions are applied by Cortex XDR. - Response is concatenated using AND condition (OR is not supported). - Maximum result set size is 100. - Offset is the zero-based number of alerts from the start of the result set. The response indicates whether an PAN NGFW type alert contains a PCAP triggering packet. [Cortex XDR 3.x REST API – Incident Management: POST /public_api/v1/alerts/get_alerts] Available on Cortex XDR 3.x tenants (replaced by Cases / Issues on Cortex XDR 6.0 platform tenants).
- **Cortex XDR alerts update alerts** (Update). Update Alerts. Update one or more alerts. You can update up to 100 alerts per request. Missing fields are ignored. Required license: Cortex XDR Prevent, Cortex XDR Pro per Endpoint, or Cortex XDR Pro per GB [Cortex XDR 3.x REST API – Incident Management: POST /public_api/v1/alerts/update_alerts] Available on Cortex XDR 3.x tenants (replaced by Cases / Issues on Cortex XDR 6.0 platform tenants).
- **Get single Cortex XDR API key by ID** (Get). Get API Key. This endpoint retrieves an API key and its respective properties. Note: the 'roles' field refers to the 'pretty_name' attributes from the Roles APIs, not the unique role identifiers. For possible 'security_level' values, please refer to the enum documentation for 'SecurityLevel'. [Cortex XDR API – API Keys: GET /platform/iam/v1/api-key/{api_key_id}]
- **Update a Cortex XDR API key by ID** (Update). Edit an API key. This endpoint allows for the editing of an existing API key. For possible 'security_level' values, please refer to the enum documentation for 'SecurityLevel'. [Cortex XDR API – API Keys: PUT /platform/iam/v1/api-key/{api_key_id}]
- **Cortex XDR API keys bulk delete** (Delete). Delete API Keys. Delete API Keys by ID. Required license: Cortex XDR. [Cortex XDR API – API Keys: POST /public_api/v1/api_keys/delete]
- **Cortex XDR API keys generate** (Generate). Generate an API Key. Generate a new API Key and define the roles assigned to it and whether the security level is standard or advanced. Required license: Cortex XDR. [Cortex XDR API – API Keys: POST /public_api/v1/api_keys/generate]
- **List all Cortex XDR API keys** (List). Get existing API Keys. Get a list of API Keys filtered by expiration date, role, or ID. Each request returns up to 100 API keys. To retrieve more, send a first request with search_from set to 0 and read FILTER_COUNT from the response. Then page through the results with search_from and search_to until you have retrieved FILTER_COUNT keys. Required license: Cortex XDR. [Cortex XDR API – API Keys: POST /public_api/v1/api_keys/get_api_keys]
- **Create a Cortex XDR appsec application** (Create). Create an application. Creates a new application asset based on the provided details, such as name, criticality, and asset selection. Required license: Cortex XDR with the Cortex Cloud Posture Management or Cortex Cloud Runtime Security with Application Security Add-on. [Cortex XDR API – Applications: POST /public_api/appsec/v1/application]
- **Delete a Cortex XDR appsec application by ID** (Delete). Delete an application. Deletes a specific application asset identified by its unique ID. Required license: Cortex XDR with the Cortex Cloud Posture Management or Cortex Cloud Runtime Security with Application Security Add-on. [Cortex XDR API – Applications: DELETE /public_api/appsec/v1/application/{applicationId}]
- **Get single Cortex XDR appsec application by ID** (Get). Get an application. Retrieves the metadata for a specific Business Application asset using its unique ID. Required license: Cortex XDR with the Cortex Cloud Posture Management or Cortex Cloud Runtime Security with Application Security Add-on. [Cortex XDR API – Applications: GET /public_api/appsec/v1/application/{applicationId}]
- **Cortex XDR appsec application import** (Import). Bulk import applications from CSV. Creates or updates Business Application assets using CSV content included as a string in the JSON request body. Each CSV row is processed as follows: - Creates a new application if the row describes a new application. - Updates an existing application if the row matches an existing application. - Skips the row with a warning if it cannot be applied. Rows that create or update applications are processed asynchronously by a background job. [Cortex XDR API – Applications: POST /public_api/appsec/v1/application/import]
- **List all Cortex XDR appsec application** (List). Get applications. Retrieves a list of all application assets using pagination. Required license: Cortex XDR with the Cortex Cloud Posture Management or Cortex Cloud Runtime Security with Application Security Add-on. [Cortex XDR API – Applications: GET /public_api/appsec/v1/application]
- **Update a Cortex XDR appsec application by ID** (Update). Update an application. Updates the attributes of an existing application asset identified by its unique ID. Only the fields included in the request are updated; omitted fields or fields set to undefined remain unchanged. If the request does not include any updatable fields, the endpoint performs no update. Required license: Cortex XDR with the Cortex Cloud Posture Management or Cortex Cloud Runtime Security with Application Security Add-on. [Cortex XDR API – Applications: PUT /public_api/appsec/v1/application/{applicationId}]
- **Cortex XDR appsec application assets override** (Action). Add or remove assets. Adds or removes assets from the specified application. Set the operation field to ADD to associate the specified assets with the application, or to REMOVE to disassociate them. Each request creates a single override action and returns an actionId that identifies the operation and all affected assets. You can use this actionId to undo the operation with Revert asset override action. To identify assets that can be added, use List addable assets. [Cortex XDR API – Applications: POST /public_api/appsec/v1/application/{applicationId}/assets/override]
- **List all Cortex XDR appsec application assets addable** (List). List addable assets. Returns assets that can be added to the specified application. Use this endpoint to find assets that are not currently associated with the application and manually add them to improve the application's asset inventory. Use the optional filter parameter to return specific subsets of assets, such as orphan assets, recently discovered assets, or assets with shared contributors. Results are paginated, with pages starting at 1. [Cortex XDR API – Applications: GET /public_api/appsec/v1/application/{applicationId}/assets/addable]
- **Delete a Cortex XDR appsec application assets override by ID** (Delete). Revert asset override action. Reverts a manual asset override action by its actionId. Reverting an action undoes the add or remove operation for all assets affected by that override action. To find the actionId, use the value returned by Add or remove assets or the actionId value from List override actions. Required license: Cortex XDR with the Cortex Cloud Posture Management or Cortex Cloud Runtime Security with Application Security Add-on. [Cortex XDR API – Applications: DELETE /public_api/appsec/v1/application/{applicationId}/assets/overrides/{actionId}]
- **List all Cortex XDR appsec application assets overrides** (List). List override actions. Returns the history of manual asset override actions for the specified application. Each entry represents a single add or remove action and includes the affected assets, the operation, the user who performed it, and the timestamp when it was created. Results are paginated, with pages starting at 1. Required license: Cortex XDR with the Cortex Cloud Posture Management or Cortex Cloud Runtime Security with Application Security Add-on. [Cortex XDR API – Applications: GET /public_api/appsec/v1/application/{applicationId}/assets/overrides]
- **List all Cortex XDR appsec application assets removable** (List). List removable assets. Returns assets that can be removed from the specified application. Use this endpoint to identify assets that are currently associated with the application and are eligible for manual removal. Results are paginated, with pages starting at 1. Required license: Cortex XDR with the Cortex Cloud Posture Management or Cortex Cloud Runtime Security with Application Security Add-on. [Cortex XDR API – Applications: GET /public_api/appsec/v1/application/{applicationId}/assets/removable]
- **List all Cortex XDR appsec application configuration** (List). Get an application configuration. Retrieves the application configuration settings. Required license: Cortex XDR with the Cortex Cloud Posture Management or Cortex Cloud Runtime Security with Application Security Add-on. [Cortex XDR API – Applications: GET /public_api/appsec/v1/application/configuration]
- **Create a Cortex XDR appsec application criterion** (Create). Create a Criteria. Creates a Criteria based on the provided details. Required license: Cortex XDR with the Cortex Cloud Posture Management or Cortex Cloud Runtime Security with Application Security Add-on. [Cortex XDR API – Criteria: POST /public_api/appsec/v1/application/criteria]
- **Delete a Cortex XDR appsec application criterion by ID** (Delete). Delete a Criteria. Deletes a specific criteria identified by its unique Id. Required license: Cortex XDR with the Cortex Cloud Posture Management or Cortex Cloud Runtime Security with Application Security Add-on. [Cortex XDR API – Criteria: DELETE /public_api/appsec/v1/application/criteria/{criteriaId}]
- **Get single Cortex XDR appsec application criterion by ID** (Get). Get a Criteria by ID. Retrieves detailed information for a specific criteria using its unique Id. Required license: Cortex XDR with the Cortex Cloud Posture Management or Cortex Cloud Runtime Security with Application Security Add-on. [Cortex XDR API – Criteria: GET /public_api/appsec/v1/application/criteria/{criteriaId}]
- **List all Cortex XDR appsec application criteria all** (List). Get all criteria. Retrieves a paginated list of all criteria. Required license: Cortex XDR with the Cortex Cloud Posture Management or Cortex Cloud Runtime Security with Application Security Add-on. [Cortex XDR API – Criteria: GET /public_api/appsec/v1/application/criteria/all]
- **List all Cortex XDR appsec application CSV template** (List). Download application import CSV template. Downloads a ready-to-fill CSV template for the bulk application import endpoint, POST /public_api/appsec/v1/application/import. Use the template to ensure that your import file contains the expected columns, column order, and formatting. [Cortex XDR API – Applications: GET /public_api/appsec/v1/application/csv-template]
- **List all Cortex XDR appsec attestation pipelines with signing** (List). List pipelines that perform signing. Get the IDs of the pipelines that perform artifact signing. This endpoint tells you which pipelines sign, not what the signing outcome was. The response has no status field, and the request has no filter parameter. Results are ordered by pipelineId, which is unique and never changes. This keeps paging with limit and offset stable, so pages don't overlap or drop rows. [Cortex XDR API – Attestation Pipelines: POST /public_api/appsec/v1/attestation/pipelines-with-signing]
- **Cortex XDR appsec attestation public key bulk delete** (Delete). Delete a public key. Soft-delete a public key. The key status changes to deleted. A successful call returns 200 with an empty body. Required role: Any role with the Asset Inventory (asset_management_action) or CLI Tool (ci_tool_edit) set to View/Edit. Required license: Cortex XDR Pro per Endpoint with either the Cortex XDR Cloud Posture add-on or the Cortex Cloud Runtime Security add-on, together with the Cortex XDR Application Security add-on. [Cortex XDR API – Attestation Public Keys: DELETE /public_api/appsec/v1/attestation/public-key/delete]
- **Cortex XDR appsec attestation public key bulk update** (Update). Update a public key. Update the key material or rotation period of a registered public key. Specify the key name in the query string and the changes in the request body. Both body fields are optional, so send only the fields you want to change. A successful call returns 200 with an empty body. To confirm the change, get the key. [Cortex XDR API – Attestation Public Keys: POST /public_api/appsec/v1/attestation/public-key/update]
- **Create a Cortex XDR appsec attestation public key** (Create). Add a public key. Register a new public key. The key material is validated and stored encrypted. The key owner is taken from the authenticated caller, so don't include it in the request body. The PEM must be JSON-escaped (real newlines become ). [Cortex XDR API – Attestation Public Keys: POST /public_api/appsec/v1/attestation/public-key/add]
- **Cortex XDR appsec attestation public key is key exist** (Action). Check whether a public key exists. Check whether a public key with the specified name is registered. A key that was never registered returns { "exists": false } with a 200 status. This is an answer, not an error. Required role: Any role with the Asset Inventory (asset_management) or CLI Tool (ci_tool_view) set to View. [Cortex XDR API – Attestation Public Keys: GET /public_api/appsec/v1/attestation/public-key/is-key-exist]
- **Cortex XDR appsec attestation public key is key type supported** (Action). Check whether a key type is supported. Validate a public key without registering it. This is the quickest way to check a key before you add it. An unsupported key still returns 200. The result is in the response body, not the status code. To validate a key file directly without escaping the PEM manually, run the following command, and then pass -d @body.json in your request: Required role: Any role with the Asset Inventory (asset_management) or CLI Tool (ci_tool_view) set to View. [Cortex XDR API – Attestation Public Keys: POST /public_api/appsec/v1/attestation/public-key/is-key-type-supported]
- **List all Cortex XDR appsec attestation public key** (List). Get a public key. Get the metadata and key material for a single public key. This is the only endpoint that returns the key material. Required role: Any role with the Asset Inventory (asset_management) or CLI Tool (ci_tool_view) set to View. Required license: Cortex XDR Pro per Endpoint with either the Cortex XDR Cloud Posture add-on or the Cortex Cloud Runtime Security add-on, together with the Cortex XDR Application Security add-on. [Cortex XDR API – Attestation Public Keys: GET /public_api/appsec/v1/attestation/public-key/get]
- **Cortex XDR appsec attestation public key lookup** (Action). List public keys. Get the metadata for all registered public keys. The response doesn't include key material. A tenant with no keys returns an empty array ([]). Required role: Any role with the Asset Inventory (asset_management) or CLI Tool (ci_tool_view) set to View. Required license: Cortex XDR Pro per Endpoint with either the Cortex XDR Cloud Posture add-on or the Cortex Cloud Runtime Security add-on, together with the Cortex XDR Application Security add-on. [Cortex XDR API – Attestation Public Keys: GET /public_api/appsec/v1/attestation/public-key/list]
- **List all Cortex XDR appsec attestation verify keys for pipeline** (List). List keys that verify a pipeline. Get the names of the public keys that verify a pipeline. The response never includes key material. Pipeline IDs are opaque, case-sensitive, 64-character hex strings, not org/repo/workflow names. To get valid IDs, list the pipelines that perform signing. A pipeline that exists but has never been signed returns a result with an empty keys array and a 200 status. This is a valid answer, not an error. [Cortex XDR API – Attestation Pipelines: POST /public_api/appsec/v1/attestation/verify-keys-for-pipeline]
- **List all Cortex XDR appsec billing contributors** (List). Get Billing Contributors. Returns a list of unique repository users who are considered active contributors for billing calculations. An active contributor is defined as a unique (by email), non-bot human user who has committed code within the last 90 days to a billable, non-archived repository that has at least one security scanner enabled. Note: You must have the Instance Administrator permissions to run this endpoint. [Cortex XDR API – Billing: GET /public_api/appsec/v1/billing/contributors]
- **List all Cortex XDR appsec code to cloud coverage** (List). Get Code-to-Cloud Coverage Ratio. Returns the Code-to-Cloud coverage ratio, which measures the percentage of your assets that have a traceable lineage between code and cloud. This is the same value shown on the Code to Cloud dashboard. [Cortex XDR API – Code To Cloud Coverage: GET /public_api/appsec/v1/code-to-cloud/coverage]
- **Cortex XDR appsec collectors upload** (Upload). 3rd Party AppSec Collector. Upload SAST findings from third-party security tools to Cortex Cloud Application Security using the Collector API. This endpoint is used specifically for ingesting scan results, not for creating or configuring a generic collector. The Collector API accepts scan results in SARIF v2.1.0 format. Once uploaded, the SARIF file is parsed to create code findings. [Cortex XDR API – Data Sources: POST /public_api/appsec/v1/collectors/{collectorId}]
- **Create a Cortex XDR appsec data source instance** (Create). Create AppSec Data Sources. Create a new data source instance to connect an external system to your Cortex environment. Required license: Cortex XDR with the Cortex Cloud Posture Management or Cortex Cloud Runtime Security with Application Security Add-on. [Cortex XDR API – Data Sources: POST /public_api/appsec/v1/data_source_instances]
- **Delete a Cortex XDR appsec data source instance by ID** (Delete). Delete an AppSec Data Source. Delete the specified data source instance from your Cortex environment. Required license: Cortex XDR with the Cortex Cloud Posture Management or Cortex Cloud Runtime Security with Application Security Add-on. [Cortex XDR API – Data Sources: DELETE /public_api/appsec/v1/data_source_instances/{id}]
- **Get single Cortex XDR appsec data source instance by ID** (Get). Get an AppSec Data Source. Retrieve the details of a specific data source instance identified by its ID. Required license: Cortex XDR with the Cortex Cloud Posture Management or Cortex Cloud Runtime Security with Application Security Add-on. [Cortex XDR API – Data Sources: GET /public_api/appsec/v1/data_source_instances/{id}]
- **List all Cortex XDR appsec data source instances** (List). Get all Data Sources. Retrieve a list of all data source instances configured in your Cortex environment. You can filter the results by data source type and category. Required license: Cortex XDR with the Cortex Cloud Posture Management or Cortex Cloud Runtime Security with Application Security Add-on. [Cortex XDR API – Data Sources: GET /public_api/appsec/v1/data_source_instances]
- **Update a Cortex XDR appsec data source instance by ID** (Update). Update an AppSec Data Source. Update the configuration of an existing data source instance. Required license: Cortex XDR with the Cortex Cloud Posture Management or Cortex Cloud Runtime Security with Application Security Add-on. [Cortex XDR API – Data Sources: PUT /public_api/appsec/v1/data_source_instances/{id}]
- ...and 393 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
