Skip to main content
Book a demo

Connect Planhat to ECA

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

Book a demo ECA setup guide

Set up

Add Planhat to ECA in four steps

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

  1. 1

    Add Planhat to Runlayer

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

    Adding a connector manually
  2. 2

    Connect ECA to Runlayer

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

    ECA setup guide
  3. 3

    Sign in to Planhat

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

  4. 4

    Use Planhat from ECA

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

Tools

10 Planhat tools in ECA

Runlayer policy decides which of these ECA users can call.

  • Create document

    Create a new document (page) in Planhat.

  • Create model record

    MODEL: "Company", PARAMETERS: {"name": "Acme Corp", "domain": "acme.com"}

  • Delete model record

    Delete existing record.

  • Get document

    Retrieve a document (page) by its ID, including its full content.

  • Get model action parameters

    Returns field metadata (names, types, required flags) for a data model.

  • Get model record

    Get single record by ID.

  • List model records

    MODEL: "Company", LIMIT: 20

  • Search documents

    Search documents (pages) by text.

See all 10 Planhat 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 Planhat 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