Runlayer Plugin
Unified endpoint
Add one remote MCP endpoint. Users discover and authorize the approved tools available to them without accumulating separate client configurations.
Runlayer for Claude Code
Route Claude Code through approved MCPs with local-tool enforcement, full session telemetry, and managed model routing.
01
Connect
Give everyone in Claude Code 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.
Direct connection
Per-connector endpoint
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
02
Observe
See how Claude Code is being used
Runlayer uses every channel Claude Code exposes. Each one is labeled, so you can tell real-time hooks from after-the-fact imports.
Client hooks
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Read the guideAnthropic inference hooks
With Claude Enterprise, Anthropic sends each governed Claude Code prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).
Read the guideOTLP telemetry
Claude Code can export OpenTelemetry logs to Runlayer for observe-only session reconstruction.
Read the guide03
Enforce
Know exactly what Claude Code can block
Each row reflects Runlayer’s enforcement code for Claude Code: 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 Claude Code runs it. |
| Post-tool output block | Supported | Runlayer can block a tool’s output before Claude Code’s model sees it. |
| Output rewrite | Supported | Runlayer can mask sensitive parts of a tool’s output in Claude Code and pass the rest through. |
Enforcement postureManaged device
Minimum supported versionNo minimum listed
Client-specific caveats
- When a tool fails, Runlayer records the error but cannot hide it.
04
Deploy at scale
Roll out Claude Code controls with the tools IT already uses
Admins can deploy the Runlayer CLI and endpoint package through MDM, then keep approved MCP configuration in sync automatically.
macOSmacOSWindows and macOS
SimpleMDM
Open deployment guide →
Jamf Pro
Open deployment guide →
Microsoft Intune
Open deployment guide →
One signed package, settings managed centrally
Runlayer’s endpoint package installs on managed macOS and Windows devices. It discovers shadow AI, keeps hooks in place, captures sessions, and applies runtime controls. Approved MCP configuration re-syncs on a schedule for supported clients.
MCP servers
Connect Claude Code to the tools your teams use
Setup steps, tools, and controls for each MCP server in Claude Code.
