Skip to content

Connectors · Identity & security

Palo Alto Networks Cortex XDR MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Palo Alto Networks Cortex XDR and the rest of your systems. It gives your agent 117 Palo Alto Networks Cortex XDR actions (53 reads, 48 writes and 16 that wait for a confirmation) and holds the Palo Alto Networks Cortex XDR credential itself, so the agent never does. It paces Palo Alto Networks Cortex XDR's limits and records every call.

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "palo_alto_cortex_xdr.endpoints.list",  intent: "check which Palo Alto Networks Cortex XDR account is connected"}# Get Endpoint · read · 1 upstream call
  • 117actionsin one signed file
  • 53readlook, never change
  • 48writecreate and update
  • 16wait for a yesdestructive, confirmed first

Set up

Connect Palo Alto Networks Cortex XDR in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect Palo Alto Networks Cortex XDR.

    Header credentials. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.

    • api_keyCortex XDR Standard API key
    • api_key_idThe key's ID from the ID column of the API Keys table
    • hostWhere your Palo Alto Networks Cortex XDR lives: your host
    account { op: "connections.requirements", service: "palo_alto_cortex_xdr" }
    # free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "palo_alto_cortex_xdr.endpoints.list" }# get endpoint · read · 1 upstream callcheck { action: "palo_alto_cortex_xdr.endpoints.delete", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Palo Alto Networks Cortex XDR at a glance

Sign-in
Header credentials. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide
api_keyapi_key_id
Setup fields
host
Limits we pace to
10 calls a second, per connection
API covered
Cortex XDR 3.x REST API (OpenAPI 3.0, doc version 3.18), at your Palo Alto Networks Cortex XDR instance's API base URL, which you enter when connecting
Built from
Palo Alto Networks Cortex XDR's documentation, read 23 October 2026cortex-docs.paloaltonetworks.comcortex-docs.paloaltonetworks.comcortex-docs.paloaltonetworks.com
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
53 of 53 reads, for up to 5 minutes; a write clears what it affects
Shared entities
6, so ask can line Palo Alto Networks Cortex XDR up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Palo Alto Networks Cortex XDR.

117 actions in 35 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 53readlook, never change
  • 48writecreate and update
  • 16destructivewait for a confirmation
  1. Endpoints

    13

    3 read · 7 write · 3 destructive

    Get Endpoint · Delete Endpoints · Get all Endpoints · Retrieve File

  2. Alerts

    7

    4 read · 3 write · 0 destructive

    Get all Alerts · Update Alerts · Retrieve PCAP Packet · Insert CEF Alerts

  3. Brokers

    7

    1 read · 4 write · 2 destructive

    Generate a Broker VM registration token · List registered Broker VMs · Reboot a Broker VM · Edit a Broker VM

  4. Distributions

    6

    4 read · 1 write · 1 destructive

    Create distributions · Get Distributions · Get Distribution version · Get Distribution status

  5. Authentication settings

    5

    2 read · 2 write · 1 destructive

    Get authentication settings for all configured domains · Create authentication settings for IdP SSO or metadata URL · Update authentication settings · Delete authentication settings by domain

  6. Broker applets

    5

    1 read · 4 write · 0 destructive

    Trigger an immediate Network Mapper scan · Activate an applet with a configuration · Edit an applet's configuration · Deactivate an applet

  7. Disable prevention rules

    5

    2 read · 2 write · 1 destructive

    Add Disable Prevention Rule · Get Disable Prevention Rules · Get Disable Prevention Modules · Edit Disable Prevention Rule

  8. Legacy exceptions

    5

    2 read · 2 write · 1 destructive

    Add Legacy Exception Rule · Fetch Legacy Exception Rules · Get Legacy Exceptions Modules · Edit Legacy Exception Rule

27 more areas · 64 actions
  • Scripts 5
  • Syslog servers 5
  • Endpoint tags 4
  • Featured fields 4
  • Prevention profiles 4
  • Datasets 3
  • Disable injection prevention rules 3
  • Incidents 3
  • Lookup data 3
  • Risk 3
  • Script executions 3
  • XQL queries 3
  • Actions 2
  • Broker log bundles 2
  • Hash exceptions 2
  • Indicators 2
  • System 2
  • Users 2
  • Audit agent reports 1
  • Audit management logs 1
  • Broker actions 1
  • Device control violations 1
  • Endpoint profiles 1
  • Quarantine 1
  • Roles 1
  • Triage presets 1
  • User groups 1

Top actions

The Palo Alto Networks Cortex XDR API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 23 of Palo Alto Networks Cortex XDR's 23 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
palo_alto_cortex_xdr.users.listGet UsersGet Users.readidentity.user.list474 connectors
palo_alto_cortex_xdr.user_groups.listGet User GroupsGet User Groups.readidentity.group.list262 connectors
palo_alto_cortex_xdr.roles.listGet RolesGet Roles.readidentity.role.list184 connectors
palo_alto_cortex_xdr.endpoints.listGet EndpointGet Endpoint.readdevice.endpoint.list65 connectors
palo_alto_cortex_xdr.alerts.listGet all AlertsGet all Alerts.readsecurity.alert.list22 connectors
palo_alto_cortex_xdr.incidents.listGet all IncidentsGet all Incidents.readsecurity.incident.list17 connectors
palo_alto_cortex_xdr.audit_management_logs.listGet Audit Management LogGet Audit Management Log.readsecurity.audit_log.list69 connectors
palo_alto_cortex_xdr.incidents.getGet Extra Incident DataGet Extra Incident Data.readsecurity.incident.get17 connectors
palo_alto_cortex_xdr.endpoints.deleteDelete EndpointsDelete Endpoints.destructivedevice.endpoint.delete35 connectors
palo_alto_cortex_xdr.incidents.updateUpdate an IncidentUpdate an Incident.writesecurity.incident.update13 connectors
palo_alto_cortex_xdr.alerts.updateUpdate AlertsUpdate Alerts.writesecurity.alert.update12 connectors
palo_alto_cortex_xdr.prevention_profiles.createAdd Prevention ProfileAdd Prevention Profile.writesecurity.policy.create25 connectors

Try it

Prompts to paste into Claude.

Each one names the Palo Alto Networks Cortex XDR actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    Which Palo Alto Networks Cortex XDR incidents are open, and how long has each been open?

    callspalo_alto_cortex_xdr.incidents.list

  2. Writewrite

    Update an Incident in Palo Alto Networks Cortex XDR. Show me exactly what you will send before you save it.

    callspalo_alto_cortex_xdr.incidents.update

Governance for Palo Alto Networks Cortex XDR

Destructive actions wait for a yes.

16 Palo Alto Networks Cortex XDR actions are destructive. These are all of them:

  • Delete Endpointspalo_alto_cortex_xdr.endpoints.delete
  • Delete authentication settings by domainpalo_alto_cortex_xdr.authentication_settings.delete
  • Delete a datasetpalo_alto_cortex_xdr.datasets.delete
  • Isolate Endpointspalo_alto_cortex_xdr.endpoints.isolate
  • Run Scriptpalo_alto_cortex_xdr.scripts.run
  • Run Snippet Code Scriptpalo_alto_cortex_xdr.scripts.run_snippet
  • Cancel Scan Endpointspalo_alto_cortex_xdr.endpoints.abort_scan
  • Set a User Rolepalo_alto_cortex_xdr.users.set_role
  • Remove a Broker VM from the tenantpalo_alto_cortex_xdr.brokers.delete
  • Shut down a Broker VMpalo_alto_cortex_xdr.brokers.shutdown
  • Remove data from a lookup datasetpalo_alto_cortex_xdr.lookup_data.delete
  • Delete agent installation packagespalo_alto_cortex_xdr.distributions.delete
  • Delete Tags Permanentlypalo_alto_cortex_xdr.endpoint_tags.delete
  • Delete all or filtered syslog integrationspalo_alto_cortex_xdr.syslog_servers.delete
  • Delete Legacy Exception Rulespalo_alto_cortex_xdr.legacy_exceptions.delete
  • Delete Disable Prevention Rulespalo_alto_cortex_xdr.disable_prevention_rules.delete

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

dopalo_alto_cortex_xdr.endpoints.deleteconfirm_policy: human

Delete Endpoints?

intent: the user asked me to delete Endpoints

run suspended · waiting for a named person · key palo-alto-cortex-xdr-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "palo-alto-cortex-xdr-agent",  allowed_actions: ["palo_alto_cortex_xdr.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "palo_alto_cortex_xdr.endpoints.delete", approver: "[email protected]" },    { match: "palo_alto_cortex_xdr.authentication_settings.delete", approver: "[email protected]" },    { match: "palo_alto_cortex_xdr.datasets.delete", approver: "[email protected]" }  ]}
Illustrative. Scoped to Palo Alto Networks Cortex XDR only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Palo Alto Networks Cortex XDR costs on actionlake.

Every Palo Alto Networks Cortex XDR action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Palo Alto Networks Cortex XDR refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 117 Palo Alto Networks Cortex XDR actions
  • 117actions pageeach page of a long list is one call
  • 53reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Palo Alto Networks Cortex XDR action.

117 actions by area: the id your agent calls, what it does, and its effect.

Endpoints13
  • palo_alto_cortex_xdr.endpoints.abort_scanCancel Scan Endpointsdestructive
  • palo_alto_cortex_xdr.endpoints.deleteDelete Endpointsdestructive
  • palo_alto_cortex_xdr.endpoints.get_policyGet Policyread
  • palo_alto_cortex_xdr.endpoints.isolateIsolate Endpointsdestructive
  • palo_alto_cortex_xdr.endpoints.listGet Endpointread
  • palo_alto_cortex_xdr.endpoints.list_allGet all Endpointsread
  • palo_alto_cortex_xdr.endpoints.quarantine_fileQuarantine Fileswrite
  • palo_alto_cortex_xdr.endpoints.restore_fileRestore Filewrite
  • palo_alto_cortex_xdr.endpoints.retrieve_fileRetrieve Filewrite
  • palo_alto_cortex_xdr.endpoints.scanScan Endpointswrite
  • palo_alto_cortex_xdr.endpoints.set_aliasSet an Endpoint Aliaswrite
  • palo_alto_cortex_xdr.endpoints.triageInitiate Forensics Triagewrite
  • palo_alto_cortex_xdr.endpoints.unisolateUnisolate Endpointswrite
Alerts7
  • palo_alto_cortex_xdr.alerts.get_pcapRetrieve PCAP Packetread
  • palo_alto_cortex_xdr.alerts.insert_cefInsert CEF Alertswrite
  • palo_alto_cortex_xdr.alerts.insert_parsedInsert Parsed Alertswrite
  • palo_alto_cortex_xdr.alerts.listGet all Alertsread
  • palo_alto_cortex_xdr.alerts.list_multi_eventsGet Alerts Multi-Events v2read
  • palo_alto_cortex_xdr.alerts.list_multi_events_v1Get Alerts Multi-Events v1read
  • palo_alto_cortex_xdr.alerts.updateUpdate Alertswrite
Brokers7
  • palo_alto_cortex_xdr.brokers.create_registration_tokenGenerate a Broker VM registration tokenwrite
  • palo_alto_cortex_xdr.brokers.deleteRemove a Broker VM from the tenantdestructive
  • palo_alto_cortex_xdr.brokers.listList registered Broker VMsread
  • palo_alto_cortex_xdr.brokers.rebootReboot a Broker VMwrite
  • palo_alto_cortex_xdr.brokers.shutdownShut down a Broker VMdestructive
  • palo_alto_cortex_xdr.brokers.updateEdit a Broker VMwrite
  • palo_alto_cortex_xdr.brokers.upgradeUpgrade a Broker VM to the latest available versionwrite
Distributions6
  • palo_alto_cortex_xdr.distributions.createCreate distributionswrite
  • palo_alto_cortex_xdr.distributions.deleteDelete agent installation packagesdestructive
  • palo_alto_cortex_xdr.distributions.get_statusGet Distribution statusread
  • palo_alto_cortex_xdr.distributions.get_urlGet Distribution URLread
  • palo_alto_cortex_xdr.distributions.listGet Distributionsread
  • palo_alto_cortex_xdr.distributions.list_versionsGet Distribution versionread
Authentication settings5
  • palo_alto_cortex_xdr.authentication_settings.createCreate authentication settings for IdP SSO or metadata URLwrite
  • palo_alto_cortex_xdr.authentication_settings.deleteDelete authentication settings by domaindestructive
  • palo_alto_cortex_xdr.authentication_settings.get_metadataGet IdP metadataread
  • palo_alto_cortex_xdr.authentication_settings.listGet authentication settings for all configured domainsread
  • palo_alto_cortex_xdr.authentication_settings.updateUpdate authentication settingswrite
Broker applets5
  • palo_alto_cortex_xdr.broker_applets.activateActivate an applet with a configurationwrite
  • palo_alto_cortex_xdr.broker_applets.configureEdit an applet's configurationwrite
  • palo_alto_cortex_xdr.broker_applets.deactivateDeactivate an appletwrite
  • palo_alto_cortex_xdr.broker_applets.getGet an applet's configuration and statusread
  • palo_alto_cortex_xdr.broker_applets.network_mapper_scan_nowTrigger an immediate Network Mapper scanwrite
Disable prevention rules5
  • palo_alto_cortex_xdr.disable_prevention_rules.createAdd Disable Prevention Rulewrite
  • palo_alto_cortex_xdr.disable_prevention_rules.deleteDelete Disable Prevention Rulesdestructive
  • palo_alto_cortex_xdr.disable_prevention_rules.listGet Disable Prevention Rulesread
  • palo_alto_cortex_xdr.disable_prevention_rules.list_modulesGet Disable Prevention Modulesread
  • palo_alto_cortex_xdr.disable_prevention_rules.updateEdit Disable Prevention Rulewrite
Legacy exceptions5
  • palo_alto_cortex_xdr.legacy_exceptions.createAdd Legacy Exception Rulewrite
  • palo_alto_cortex_xdr.legacy_exceptions.deleteDelete Legacy Exception Rulesdestructive
  • palo_alto_cortex_xdr.legacy_exceptions.listFetch Legacy Exception Rulesread
  • palo_alto_cortex_xdr.legacy_exceptions.list_modulesGet Legacy Exceptions Modulesread
  • palo_alto_cortex_xdr.legacy_exceptions.updateEdit Legacy Exception Rulewrite
Scripts5
  • palo_alto_cortex_xdr.scripts.getGet Script Metadataread
  • palo_alto_cortex_xdr.scripts.get_codeGet Script Coderead
  • palo_alto_cortex_xdr.scripts.listGet Scriptsread
  • palo_alto_cortex_xdr.scripts.runRun Scriptdestructive
  • palo_alto_cortex_xdr.scripts.run_snippetRun Snippet Code Scriptdestructive
Syslog servers5
  • palo_alto_cortex_xdr.syslog_servers.createCreate a syslog integrationwrite
  • palo_alto_cortex_xdr.syslog_servers.deleteDelete all or filtered syslog integrationsdestructive
  • palo_alto_cortex_xdr.syslog_servers.listGet all or filtered syslog serversread
  • palo_alto_cortex_xdr.syslog_servers.testTest syslog integrationread
  • palo_alto_cortex_xdr.syslog_servers.updateUpdate a syslog integrationwrite
Endpoint tags4
  • palo_alto_cortex_xdr.endpoint_tags.assignAssign Tagswrite
  • palo_alto_cortex_xdr.endpoint_tags.createCreate Tagwrite
  • palo_alto_cortex_xdr.endpoint_tags.deleteDelete Tags Permanentlydestructive
  • palo_alto_cortex_xdr.endpoint_tags.removeRemove Tagswrite
Featured fields4
  • palo_alto_cortex_xdr.featured_fields.replace_ad_groupsReplace Featured Active Directory Groupswrite
  • palo_alto_cortex_xdr.featured_fields.replace_hostsReplace Featured Hostswrite
  • palo_alto_cortex_xdr.featured_fields.replace_ip_addressesReplace Featured IP Addresseswrite
  • palo_alto_cortex_xdr.featured_fields.replace_usersReplace Featured Userswrite
Prevention profiles4
  • palo_alto_cortex_xdr.prevention_profiles.add_signer_cn_to_allowlistAdd Signer CN to Allowlistwrite
  • palo_alto_cortex_xdr.prevention_profiles.createAdd Prevention Profilewrite
  • palo_alto_cortex_xdr.prevention_profiles.list_modulesGet Prevention Profile Modulesread
  • palo_alto_cortex_xdr.prevention_profiles.updateEdit Prevention Profilewrite
Datasets3
  • palo_alto_cortex_xdr.datasets.createAdd Datasetwrite
  • palo_alto_cortex_xdr.datasets.deleteDelete a datasetdestructive
  • palo_alto_cortex_xdr.datasets.listGet all datasetsread
Disable injection prevention rules3
  • palo_alto_cortex_xdr.disable_injection_prevention_rules.createAdd Disable Injection and Prevention rulewrite
  • palo_alto_cortex_xdr.disable_injection_prevention_rules.disableDisable Disable Injection and Prevention Ruleswrite
  • palo_alto_cortex_xdr.disable_injection_prevention_rules.listGet Disable Injection and Prevention rulesread
Incidents3
  • palo_alto_cortex_xdr.incidents.getGet Extra Incident Dataread
  • palo_alto_cortex_xdr.incidents.listGet all Incidentsread
  • palo_alto_cortex_xdr.incidents.updateUpdate an Incidentwrite
Lookup data3
  • palo_alto_cortex_xdr.lookup_data.deleteRemove data from a lookup datasetdestructive
  • palo_alto_cortex_xdr.lookup_data.listGet data from a lookup datasetread
  • palo_alto_cortex_xdr.lookup_data.upsertAdd or update data in a lookup datasetwrite
Risk3
  • palo_alto_cortex_xdr.risk.get_scoreGet Risk Scoreread
  • palo_alto_cortex_xdr.risk.list_risky_hostsGet Risky Hostsread
  • palo_alto_cortex_xdr.risk.list_risky_usersGet Risky Usersread
Script executions3
  • palo_alto_cortex_xdr.script_executions.get_result_files_linkGet Script Execution Result Filesread
  • palo_alto_cortex_xdr.script_executions.get_resultsGet Script Execution Resultsread
  • palo_alto_cortex_xdr.script_executions.get_statusGet Script Execution Statusread
XQL queries3
  • palo_alto_cortex_xdr.xql_queries.get_quotaGet XQL Query Quotaread
  • palo_alto_cortex_xdr.xql_queries.get_resultsGet XQL Query Resultsread
  • palo_alto_cortex_xdr.xql_queries.startStart an XQL Querywrite
Actions2
  • palo_alto_cortex_xdr.actions.get_file_retrieval_detailsFile Retrieval Detailsread
  • palo_alto_cortex_xdr.actions.get_statusGet Action Statusread
Broker log bundles2
  • palo_alto_cortex_xdr.broker_log_bundles.generateRequest asynchronous log-bundle collection from a brokerwrite
  • palo_alto_cortex_xdr.broker_log_bundles.get_statusPoll the status of a log-bundle requestread
Hash exceptions2
  • palo_alto_cortex_xdr.hash_exceptions.allowlistAllow List Fileswrite
  • palo_alto_cortex_xdr.hash_exceptions.blocklistBlock List Fileswrite
Indicators2
  • palo_alto_cortex_xdr.indicators.insertInsert Simple Indicators, JSONwrite
  • palo_alto_cortex_xdr.indicators.insert_csvInsert Simple Indicators, CSVwrite
System2
  • palo_alto_cortex_xdr.system.get_tenant_infoGet Tenant Inforead
  • palo_alto_cortex_xdr.system.healthcheckSystem Health Checkread
Users2
  • palo_alto_cortex_xdr.users.listGet Usersread
  • palo_alto_cortex_xdr.users.set_roleSet a User Roledestructive
Audit agent reports1
  • palo_alto_cortex_xdr.audit_agent_reports.listGet Audit Agent Reportread
Audit management logs1
  • palo_alto_cortex_xdr.audit_management_logs.listGet Audit Management Logread
Broker actions1
  • palo_alto_cortex_xdr.broker_actions.get_statusPoll the status of an asynchronous broker actionread
Device control violations1
  • palo_alto_cortex_xdr.device_control_violations.listGet Violationsread
Endpoint profiles1
  • palo_alto_cortex_xdr.endpoint_profiles.listGet endpoint security profilesread
Quarantine1
  • palo_alto_cortex_xdr.quarantine.get_statusGet Quarantine Statusread
Roles1
  • palo_alto_cortex_xdr.roles.listGet Rolesread
Triage presets1
  • palo_alto_cortex_xdr.triage_presets.listGet triage presetsread
User groups1
  • palo_alto_cortex_xdr.user_groups.listGet User Groupsread

Questions

The Palo Alto Networks Cortex XDR MCP server, answered.

Is there a Palo Alto Networks Cortex XDR MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 117 Palo Alto Networks Cortex XDR actions across endpoints, alerts, brokers and distributions, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Palo Alto Networks Cortex XDR.

What do I need to connect Palo Alto Networks Cortex XDR?

Cortex XDR Standard API key and The key's ID from the ID column of the API Keys table. Plus your host. The free call account { op: "connections.requirements", service: "palo_alto_cortex_xdr" } lists exactly what to paste.

Can an AI agent delete or change things in Palo Alto Networks Cortex XDR?

Only if its key allows it, and only with an explicit confirmation. 16 Palo Alto Networks Cortex XDR actions are destructive, including delete Endpoints, delete authentication settings by domain and delete a dataset. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Palo Alto Networks Cortex XDR API limit?

actionlake paces every call to the limits in the Palo Alto Networks Cortex XDR service file: 10 calls a second per connection. Repeated reads are answered from cache (53 Palo Alto Networks Cortex XDR actions can be), which never reaches Palo Alto Networks Cortex XDR.

What does a Palo Alto Networks Cortex XDR action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (117 Palo Alto Networks Cortex XDR actions page). Cache hits, searches, dry runs and calls Palo Alto Networks Cortex XDR refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Palo Alto Networks Cortex XDR API does it cover?

The Cortex XDR 3.x REST API (OpenAPI 3.0, doc version 3.18) at your Palo Alto Networks Cortex XDR instance's API base URL, which you enter when connecting. It is built from Palo Alto Networks Cortex XDR's documentation as read on 23 October 2026. 117 actions in 35 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my Palo Alto Networks Cortex XDR data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Palo Alto Networks Cortex XDR credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

Give your agent Palo Alto Networks Cortex XDR today.

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.