> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.method.security/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.method.security/_mcp/server.

# Run Tools through a portal

> Create a portal between Jackals and route Tool traffic through a host with access to your destination

Portals link Jackals in your Environment and route network traffic between them through Method. Use them to reach services accessible from another host while keeping your Tools on the host where you run them.

This guide walks you through using a portal as a SOCKS5 proxy. You'll run a Tool on a source host and route its traffic through a target Jackal that can reach the destination service. This workflow lets you reach internal services, keep Tool binaries off sensitive hosts, or access external services through a host with the outbound access you need.

---

## Before you begin

You need:

* An [Operation](/guides/operator/run-your-first-operation) in which to run your Tool
* Two hosts with [Jackals installed](/guides/platform-setup/install-a-jackal) in your Environment
* A target Jackal that can reach the destination service
* A Bring Your Own Tool (BYOT) built with the Courier Compiler

> **Note**
>
> To create a BYOT Tool, see [Create and publish a Tool](/guides/tools/create-and-publish-a-tool).

## Create a portal

### 1. Choose the source and target

In your Operation, open **Network Map** and select **Create Portal**. Choose a source host and its Jackal, then a target host and its Jackal.

* **Source**: The host where your Tool runs and its traffic enters the portal
* **Target**: The host whose Jackal connects to the destination service, also called the egress Jackal

The target host is the host forwarding traffic, not the destination service itself.

In this example, the source host runs **Source Jackal**, and the target host runs **Target Jackal**. The preview shows the path between them through Method.

![Portal builder showing Source Jackal and Target Jackal, with a preview of the path through Method](/_fern-files/_img/0a6893da87b20feee4f490b2f16c2956735922d0dbed4f66afb93cc76c39bd8b.webp)

### 2. Review and create the portal

Click **Review portal**. Review the source and target, then create the portal.

Advanced settings let you change the listening port and duration. The defaults are port **1080** and **one hour**. Wait until the portal is ready before running a Tool through it.

![Network Map showing a portal connecting two hosts, with Source Jackal, Target Jackal, Active status, and port 1080 in the portal details](/_fern-files/_img/d429213f8ebecaf677f64d13ccdbbdcf742e2d93152a2c6c4b0068ca7c955f10.webp)

## Run a Tool through the portal

Configure your BYOT Tool to run on the source Jackal. Select the input Objects and set any Tool parameters, then open **Run via portal**.

Select the portal by its listening port and egress Jackal. In this example, select **Port 1080 → Egress: Target Jackal**.

![Tool configuration showing the Run via portal menu with Port 1080 and Target Jackal as an available option](/_fern-files/_img/2687236ce4bec3f6b8172a78f21742d1ec2aed927a479f679f4dce506e29319c.webp)

Click **Run**. The Tool executes on the source host, and its traffic reaches the destination through the target Jackal.

## Verify the execution used the portal

Find the Tool execution in the Operation graph. The portal icon identifies executions that ran through a portal. Hover over the icon to see **Ran via portal**, the listening port, and the egress Jackal.

![DNS Sweeper execution with a Ran via portal tooltip showing port 1080 and Target Jackal as the egress Jackal](/_fern-files/_img/002e26d8d4d6e373a0b9e4fdcd77df153af28ef62187f3a78f321319a707ffef.webp)

In this example, the Tool ran on the source host using **Source Jackal**. The portal listened on port **1080** at the source, and **Target Jackal** connected to the destination service.