ARX connectors are not API wrappers. Each one is a governance-aware integration that classifies operations by risk level, enforces per-agent permission scope, and captures structured compliance metadata from every call. Your agents use the tools they already call — with full governance wrapped around every action.
Every API call your agent makes passes through the ARX policy engine before it reaches the external system. Not logged after the fact — evaluated before it runs.
ARX knows that CrowdStrike contain_host is a higher-risk operation than get_detections. That classification is built into each connector. The policy engine uses it to decide what to permit, escalate, or block — automatically.
Every connector call writes structured metadata to the audit trail — system, operation, data type, risk score, human approval if required, result. This is what makes the Compliance Package Generator work.
Full governance layer. Available day one.
The following tools are supported via the ARX connector framework. Governance features (policy enforcement, audit trail, human approval gates) apply to all integrations. Tier 1 connectors include full security-domain risk classification. All others use the standard governance layer.
ARX accepts agents that connect via the Model Context Protocol (MCP) — the emerging industry standard for agent-to-tool connectivity supported by Anthropic, OpenAI, Google, and Microsoft. Any MCP-connected agent gets the full ARX governance layer: policy enforcement, audit logging, and human approval gates.
Security-domain risk classification built in. Know that contain_host is higher risk than get_detections. Full compliance metadata capture. Per-agent scope binding. Auto-generated compliance documentation.
Universal governance for any MCP-compatible tool. Policy enforcement, audit logging, and human approval gates applied to every call. Standard risk classification. The long tail of tools — governed.
Read operations. Data queries. Status checks. Alert retrieval. These are logged to the audit trail and permitted automatically. No human intervention required. Examples: Splunk search execution, Wiz vulnerability query, Jira issue retrieval.
Write operations and status changes. Ticket creation, incident updates, alert triggering. Configurable per agent — permit automatically or route to Slack for human review depending on your policy rules. Examples: ServiceNow incident creation, PagerDuty alert trigger, Jira status transition.
Operational actions with immediate real-world consequences. These pause agent execution and route to a human approver via Slack before any action is taken. Examples: CrowdStrike host containment, Okta session revocation, Splunk SOAR playbook execution.