Skip to main content

Connect Gumloop to ECA

Give ECA governed access to Gumloop’s 45 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add Gumloop to ECA in four steps

Admins approve the server once. Everyone in ECA then gets it through the same governed connection.

  1. 1

    Approve Gumloop in Runlayer

    Add Gumloop from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect ECA to Runlayer

    Users add the Runlayer Plugin to ECA by following Runlayer’s setup guide. ECA reaches Gumloop’s 45 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    ECA setup guide
  3. 3

    Sign in to Gumloop

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

  4. 4

    Use Gumloop from ECA

    Gumloop’s approved tools appear in ECA. Every call is checked against policy and recorded.

Tools

45 Gumloop tools in ECA

Runlayer policy decides which of these ECA users can call.

  • List agents

    List agents in your Gumloop account, with optional search and workspace filtering.

  • Get agent

    Fetch a single Gumloop agent's configuration by its ID.

  • Ask gummie

    Ask questions and get AI-powered answers from Gumloop documentation.

  • Attach agent MCP server

    Attach an MCP server (connector) to a Gumloop agent, or update its configuration if already attached.

  • Attach agent skills

    Attach one or more existing skills to a Gumloop agent.

  • Call MCP tool

    Execute a single tool on a connected MCP server.

  • Cancel session

    Cancel an in-progress Gumloop agent session.

  • Create agent

    Create a new Gumloop agent with a name, model, and optional configuration.

See all 45 Gumloop tools

Control

What Runlayer can see and stop in ECA

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

  • Gateway policy (available)

    Every Gumloop call from ECA passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

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

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for ECA yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination