G2

Verified User in Business Supplies and Equipment

Enterprise (> 1000 emp.)

10/7/2026

"Centralized, Okta-Backed AI Tool Governance with Strong Guardrails"

5/5

What do you like best about Runlayer?

Runlayer gives us a single, governed place to connect AI tools to the systems our teams already use. Employees can self-serve MCP connections (Glean, Notion, Jira, and others) through one Okta-backed portal. From a security standpoint, it enables centralized review, access control, audit logging, and runtime guardrails like PII and prompt-injection scanning. Its shadow-AI detection also flags MCPs running outside the approved set, which helps us roll out AI tooling quickly without losing visibility into what’s touching company data.

Onboarding has been straightforward: access is granted through Okta, and users can connect tools in just a few clicks. Personally, it’s helped me connect multiple tools together and build dashboards that let me share metrics with key stakeholders. Review collected by and hosted on G2.com.

What do you dislike about Runlayer?

Reliability is the main issue. Local tool verification fails closed, so when the Runlayer API is slow or unreachable, tool calls get blocked after a timeout (about 28s) and users see a “Security Violation Detected” error. This interrupts normal work, including routine Bash commands in Claude Code, and the message doesn’t make it clear that the root cause is an outage rather than an actual policy violation.

Users have also run into intermittent MCP connection problems (for example, Jira), and it’s hard to tell whether the issue is on the MCP side or whether Runlayer itself is down. Since enforcement is moving toward blocking the non-Runlayer version of an MCP, uptime and clear status visibility matter even more. Server naming also isn’t consistent across clients (for example, the Codex allowlist), which adds unnecessary configuration confusion. Review collected by and hosted on G2.com.

What problems is Runlayer solving and how is that benefiting you?

Runlayer tackles the problem of employees connecting AI tools to company systems through unvetted MCP servers. Those connections can expose company data, and in the past our Security team had little to no visibility into what was being connected or how. With Runlayer, we get a single, reviewed catalog of approved MCPs, Okta-based access control, audit logging, and runtime scanning for risks like prompt injection and PII leakage. It also flags MCPs running outside the approved set.

For me, this means I can connect tools like Glean, Notion, and Jira to Claude through one portal, instead of waiting on a separate security review for each individual connection. I can use AI with real work systems while still knowing the integrations are vetted and monitored. Overall, it reduces the risk that a tool I rely on accidentally exposes company or customer data. Review collected by and hosted on G2.com.