Skip to main content

Connect Asana to Hermes

Give Hermes governed access to Asana’s 39 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add Asana to Hermes in four steps

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

  1. 1

    Approve Asana in Runlayer

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

  2. 2

    Connect Hermes to Runlayer

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

    Hermes setup guide
  3. 3

    Sign in to Asana

    Each user signs in to Asana with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Asana from Hermes

    Asana’s approved tools appear in Hermes. Every call is checked against policy and recorded.

Tools

39 Asana tools in Hermes

Runlayer policy decides which of these Hermes users can call.

  • Add comment

    Add a comment to a task.

  • Create project

    Create a new project with optional sections and tasks in a single operation.

  • Create project confirm

    DEPRECATED; DO NOT USE.

  • Create project confirm populate

    DEPRECATED; DO NOT USE.

  • Create project from template

    Create a project from a project template.

  • Create project preview v3

    Show a visual preview of a project structure before the project is created in Asana.

  • Create project status update

    Post a status update to a project or portfolio.

  • Create task confirm

    DEPRECATED; DO NOT USE.

See all 39 Asana tools

Control

What Runlayer can see and stop in Hermes

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, Hermes 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 before Hermes runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output in Hermes and show a message in its place.

  • Redact output in place (not available)

    Hermes cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

In Hermes

  • Hermes can replace blocked tool output with a message, but its after-call event is for monitoring only.

Frequently asked questions

Connect more

Find another combination