Runlayer for Gemini CLI

Connect Gemini CLI to local and remote MCP servers with hooks, enforcement, and Sessions support.

Connect

Give everyone in Gemini 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 Gemini 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 Gemini 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 Gemini CLI runs it.
Post-tool output block	Supported	Runlayer can block a tool’s output before Gemini CLI’s model sees it.
Output rewrite	Unsupported	Gemini CLI can only add text to a tool result, not replace it, so Runlayer blocks output it would otherwise mask.

Enforcement postureManaged device

Minimum supported version0.26.0

When Runlayer blocks a call or its output, Gemini CLI shows the model the block reason instead.
Runlayer can rewrite a tool’s inputs before Gemini CLI runs it.
Hooks need Gemini CLI 0.26.0 or newer; older versions ignore them.
Failed tool calls are checked the same way as successful ones.

MCP servers

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