Skip to main content
Book a demo

Connect RunReveal to Cline CLI

Give Cline CLI governed access to RunReveal’s 53 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Cline CLI setup guide

Set up

Add RunReveal to Cline CLI in four steps

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

  1. 1

    Add RunReveal to Runlayer

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

    Adding a connector manually
  2. 2

    Connect Cline CLI to Runlayer

    Users add the Runlayer Plugin to Cline CLI by following Runlayer’s setup guide. Cline CLI reaches RunReveal’s 53 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Cline CLI setup guide
  3. 3

    Sign in to RunReveal

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

  4. 4

    Use RunReveal from Cline CLI

    RunReveal’s approved tools appear in Cline CLI. Every call is checked against policy and recorded.

Tools

53 RunReveal tools in Cline CLI

Runlayer policy decides which of these Cline CLI users can call.

  • List agent resources

    List built-in reference documents available to load with AgentResourcesLoad.

  • Agent resources load

    Load a built-in reference document by uri.

  • Create agent skills

    Create a new agent skill in this workspace.

  • List agent skills

    List the agent skills available in this workspace.

  • Agent skills load

    Load a single agent skill by name.

  • Update agent skills

    Apply a partial edit to an existing agent skill.

  • Create agents

    Create a scheduled AI agent that runs a prompt on a cron schedule.

  • Delete agents

    Delete a scheduled AI agent by id, including its auto-created role and access policies.

See all 53 RunReveal tools

Control

What Runlayer can see and stop in Cline CLI

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

  • Gateway policy (available)

    Every RunReveal call from Cline CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

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

  • Block output after it runs (not available)

    Cline CLI ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.

  • Redact output in place (not available)

    Runlayer cannot mask tool output in Cline CLI. The gateway still applies policy to the call.

In Cline CLI

  • If Runlayer’s hook times out or crashes, Cline CLI lets the tool call through.
  • This covers the Cline CLI, not the Cline extension for VS Code.

Frequently asked questions

Connect more

Find another combination