# Arcade

## Overview

Arcade is a real-time traffic processing engine that enables secure collection and forwarding of network events into Akto for runtime API visibility and analysis. This integration lets you capture API traffic and metadata from Arcade and send it into your Akto environment for security monitoring and enforcement.

The Arcade Integration automatically:

* Collects API request and response metadata from your Arcade deployment.
* Forwards structured traffic events to Akto’s Traffic Processor.
* Supports downstream security analysis and dashboard visualization in Akto.

## Steps to Connect

{% stepper %}
{% step %}
**Configure Akto Traffic Processor**

Set up and configure your Traffic Processor. The steps are mentioned [here](https://ai-security-docs.akto.io/akto-argus-agentic-ai-security-for-homegrown-ai/connectors/others/hybrid-saas).

{% hint style="warning" %}
**Important**

Keep the your Data ingestion URL ready. It will be required in the next steps.
{% endhint %}
{% endstep %}

{% step %}
**Navigate to Contextual Access in Arcade**

1. Log in to your Arcade Dashboard.
2. From the left navigation panel, select **Contextual Access**.
3. Under the **Extensions** section, click **Add Extension**.

   <div data-with-frame="true"><figure><img src="https://3128331180-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftog5ODwYfqPOf4eQhsOC%2Fuploads%2Fd3denCbywCfT4Zla4A4V%2Fimage.png?alt=media&#x26;token=c078bfca-4c3f-4fb2-a457-cf6e8e4afe3b" alt="" width="563"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}
**Create a New Webhook Extension**

In the **Add Extension** screen enter the Basic Information such as:

* **System Type:** Select `Webhook`
* **Name:** Provide a descriptive name (e.g., `Akto Security Integration`)
* **Description (optional):**\
  Example:\
  `Forwards tool execution events to Akto Traffic Processor for security analysis`
* **Scope:** Select the appropriate scope (Project or Organization)

  <div data-with-frame="true"><figure><img src="https://3128331180-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftog5ODwYfqPOf4eQhsOC%2Fuploads%2Fz1HvQ01lm87Jan1CKtaA%2Fimage.png?alt=media&#x26;token=4c65877f-7d35-41bc-891a-5229a6016ed2" alt="" width="563"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}
**Configure Webhook Endpoints**

Under **Webhook Endpoints**, configure the execution stages that should be intercepted.

{% hint style="warning" %}
**Note**

You must enter your Akto Traffic Processor ingestion URL in each enabled stage.\
All other fields can be left as default unless you require a custom configuration.
{% endhint %}

**1. Tool Access**

Enable **Tool Access** if you want Akto to control which users can see or use specific tools.

**Configure:**

* **Webhook URL:**\
  Enter your Data Ingestion ingestion endpoint:

  ```
  <your-data-ingestion-url>
  ```
* **Priority:** Leave as default (`0`) unless you need custom execution ordering.
* **On Failure:** Controls what arcade.dev does if Akto's webhook is unreachable or returns an error. Set to `Allow request` to let the tool call proceed when Akto is unavailable, or `Block request` to deny the call if Akto cannot be reached.
* **Timeout:** Leave default (recommended: 5 seconds).
* **Response Caching:** Keep disabled unless explicitly required.

  <div data-with-frame="true"><figure><img src="https://3128331180-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftog5ODwYfqPOf4eQhsOC%2Fuploads%2FfpeRPF5cj2uN3MtwJuSH%2Fimage.png?alt=media&#x26;token=b3b53499-83a0-425b-b028-ffdc6f5c7d59" alt="" width="563"><figcaption></figcaption></figure></div>

**2. Pre Tool Execution**

Enable **Pre tool execution** to validate and inspect tool inputs before the tool runs.

**Configure:**

* **Webhook URL:**

  ```
  <your-data-ingestion-url>
  ```
* Leave **Priority**, **Timeout**, and other fields as default unless you require custom behaviour.
* **On Failure:** Controls what arcade.dev does if Akto's webhook is unreachable or returns an error. Set to `Allow request` to let the tool call proceed when Akto is unavailable, or `Block request` to deny the call if Akto cannot be reached.

  <div data-with-frame="true"><figure><img src="https://3128331180-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftog5ODwYfqPOf4eQhsOC%2Fuploads%2FsxGIvphyeN7yXvyPuz86%2Fimage.png?alt=media&#x26;token=7a5cf4ba-43e1-41b1-b123-3854f7ca46f6" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="info" %}
**Blocking vs Async Mode**

* **Blocking mode (default):** Keep **Pre Tool Execution** enabled. Akto evaluates tool inputs before execution and can block unsafe or policy-violating calls.
* **Async / monitoring-only mode:** Disable **Pre Tool Execution** and rely solely on Post Tool Execution. Tool calls will not be intercepted — Akto will only observe and record outputs after execution. Use this when you want visibility without enforcement.
  {% endhint %}

**3. Post Tool Execution**

Enable **Post tool execution** to inspect tool outputs after execution.

**Configure:**

* **Webhook URL:**

  ```
  <your-data-ingestion-url>
  ```
* Leave **Priority**, **Timeout**, and other fields as default unless custom configuration is required.
* **On Failure:** Controls what arcade.dev does if Akto's webhook is unreachable or returns an error. Set to `Allow request` to let the tool call proceed when Akto is unavailable, or `Block request` to deny the call if Akto cannot be reached.

  <div data-with-frame="true"><figure><img src="https://3128331180-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftog5ODwYfqPOf4eQhsOC%2Fuploads%2FjeBmmbZoEPOVjM3O4YDc%2Fimage.png?alt=media&#x26;token=13798aa0-7ee2-40ee-807c-7f6b7cec3a52" alt="" width="563"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}
**Save and Enable the Extension**

After configuring all required webhook stages:

1. Click **Add Extension** present in the top right corner.
2. Ensure the extension is marked as **Enabled**.
3. Review the **Execution Order Preview** to confirm hooks are active.

   <div data-with-frame="true"><figure><img src="https://3128331180-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftog5ODwYfqPOf4eQhsOC%2Fuploads%2FPiIYpPlBtVDwUui5EbPO%2Fimage.png?alt=media&#x26;token=5f5634fc-9415-48ef-b06d-397f12e1b3e7" alt="" width="563"><figcaption></figcaption></figure></div>

{% endstep %}
{% endstepper %}

## Data Collected

The Arcade integration captures:

### Tool Access Events

* Tool visibility decisions
* User metadata
* Access enforcement decisions

### Pre-Execution Data

* Tool input payloads
* Validation and policy enforcement results

### Post-Execution Data

* Tool output payloads
* Redaction or blocking decisions

## Get Support

If you need assistance with the Snowflake connector:

* **In-app Chat**: Use the chat widget in your Akto dashboard for instant support
* **Discord Community**: Join our community at [discord.gg/Wpc6xVME4s](https://discord.gg/Wpc6xVME4s)
* **Email Support**: Contact us at <support@akto.io>
* **Contact Form**: Submit a support request at <https://www.akto.io/contact-us>

Our team is available 24/7 to help with setup, troubleshooting, and best practices.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ai-security-docs.akto.io/akto-argus-agentic-ai-security-for-homegrown-ai/connectors/ai-agent-security/arcade.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.