Runlayer for Cline CLI

Connect Cline CLI to Runlayer with MCP access and pre-tool enforcement where the client supports it.

Connect

Give everyone in Cline CLI the golden path to approved tools

Add one Runlayer Plugin endpoint so people find every tool they’re approved for, or connect a single server when you want a narrower set.

Runlayer Plugin

Add one remote MCP endpoint. Users discover and authorize the approved tools available to them without accumulating separate client configurations.

Direct connection

Give the client a dedicated Runlayer URL for one connector. Identity, policy, scanning, and audit still stay attached to every request.

Connection support

Remote MCP and local MCP

Observe

Runlayer uses every channel Cline CLI exposes. Each one is labeled, so you can tell real-time hooks from after-the-fact imports.

Supported

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

Enforce

Each row reflects Runlayer’s enforcement code for Cline CLI: what it can stop before a call runs, block afterward, or redact in place.

Control	Support	What that means
Pre-tool deny	Supported	Runlayer can deny a tool call before Cline CLI runs it.
Post-tool output block	Unsupported	Cline CLI ignores Runlayer after a tool runs, so Runlayer cannot block its output.
Output rewrite	Unsupported	Runlayer cannot mask tool output in Cline CLI.

Enforcement postureManaged device

Minimum supported versionNo minimum listed

Runlayer can stop a tool call only before Cline CLI runs it.
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.
Cline shortens long MCP tool names, so Runlayer treats a name it can’t match to a configured server as unknown rather than guessing.

MCP servers

Setup steps, tools, and controls for each MCP server in Cline CLI.