Skip to main content
Book a demo

Connect Adobe Marketo Engage to GitHub Copilot CLI

Give GitHub Copilot CLI governed access to Adobe Marketo Engage’s 118 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo GitHub Copilot CLI setup guide

Set up

Add Adobe Marketo Engage to GitHub Copilot CLI in four steps

Admins approve the server once. Everyone in GitHub Copilot CLI then gets it through the same governed connection.

  1. 1

    Add Adobe Marketo Engage to Runlayer

    Adobe Marketo Engage isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect GitHub Copilot CLI to Runlayer

    Users add the Runlayer Plugin to GitHub Copilot CLI by following Runlayer’s setup guide. GitHub Copilot CLI reaches Adobe Marketo Engage’s 118 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    GitHub Copilot CLI setup guide
  3. 3

    Sign in to Adobe Marketo Engage

    Sign in the way Adobe Marketo Engage requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Adobe Marketo Engage from GitHub Copilot CLI

    Adobe Marketo Engage’s approved tools appear in GitHub Copilot CLI. Every call is checked against policy and recorded.

Tools

118 Adobe Marketo Engage tools in GitHub Copilot CLI

Runlayer policy decides which of these GitHub Copilot CLI users can call.

  • Activate smart campaign

    Activate a smart campaign to start processing leads.

  • Add field set

    Add a field set (field group) to a form.

  • Add field to form

    Add a new field to a form.

  • Add field visibility rule

    Add visibility rules to a form field.

  • Add flow step

    Add a flow step to a smart campaign at the specified index.

  • Add flow step choice

    Add a conditional choice branch to an existing flow step, so the step can do different things for different leads ("if the lead is in California send email A, otherwise send email B").

  • Add leads to list

    Add existing leads to a static list (list membership).

  • Add rich text field

    Add a rich text element to a form.

See all 118 Adobe Marketo Engage tools

Control

What Runlayer can see and stop in GitHub Copilot CLI

Some controls apply to every client at the gateway. Others depend on what GitHub Copilot CLI exposes to Runlayer.

  • Gateway policy (available)

    Every Adobe Marketo Engage call from GitHub Copilot CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, GitHub Copilot CLI as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call or permission request before GitHub Copilot CLI runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before GitHub Copilot CLI’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a successful tool’s output in GitHub Copilot CLI and pass the rest through.

In GitHub Copilot CLI

  • When a tool fails, Runlayer records the error but cannot replace it.

Frequently asked questions

Connect more

Find another combination