Runlayer MCP

Runlayer MCP (the platform self-MCP) is a first-party MCP server that lets an assistant ask questions about Runlayer itself: usage analytics, audit logs, server inventory, policies, plugins, and more. It is the fastest way to answer “what happened?” and “how is adoption going?” without clicking around the UI. Runlayer MCP is not the same as Runlayer Plugin. Installing Runlayer MCP does not expose your organization’s connector MCPs — it only exposes the curated set of platform tools described below (audit logs, analytics, inventory, governance). Runlayer Plugin is the separate unified entrypoint for connector tools, and even there, connectors are exposed conditionally: only active hosted connectors the user can access through policy, never local, draft, disabled, or policy-blocked connectors.

---

​

When to use Runlayer MCP

Use Runlayer MCP when you want to:

• Pull analytics datasets for reporting (ex: top tools/users/servers over a date range)
• Query audit logs to investigate failures, policy denials, or suspicious activity
• Generate a server inventory (what MCPs exist, who can access them, what tools they expose)
• Inspect governance state (policies, access requests, security scanner settings)
• Create or maintain plugins, skills, and agents (admin / owner gated, confirm-required)

---

​

What it can do (high level)

Runlayer MCP intentionally exposes a curated set of high-leverage tools (not every backend endpoint). Common capabilities:

• Audit logs
  • Discover valid action and resource type filter values before listing or exporting audit logs
  • List recent audit events with filters (action type, resource type/id, actor, correlation id, request id, client name)
  • Fetch a single audit log entry with full details when you need deep inspection
  • Bulk export audit logs as JSON or CSV — no 90-day hot-window restriction, up to 10 000 rows per call. Non-admins are scoped to their own logs; admins see org-wide logs. Sensitive-server details are redacted unless the caller has the viewer role
• Analytics exports (admin-only)
  • Export dashboard datasets as CSV (same underlying metrics as the Analytics UI)
  • Export per-server tool health + usage breakdowns as CSV
• Servers
  • List servers you can access
  • Get server details + generate MCP client install links (Cursor / VS Code)
  • List tools/resources/prompts for a server (via Runlayer proxy)
  • Create, update, and delete servers (admin-only, confirm-required) — create_server and update_server support the same fields as the REST API, including OAuth configuration (manual and broker), audit log sensitivity, tool output offloading, MCP fingerprint, and deployment association
• Governance (mostly admin-only)
  • List, read, create, update, and delete policies (full CRUD — mutations require explicit confirm=true)
  • List access requests
  • Read/update security scanner settings (mutations require explicit confirm)
• Incidents
  • List incidents with filters (status, priority, source type, date range) and pagination
  • Get full incident details including grouped entries, available triage/remediation actions, and activity history
  • Triage incidents (resolve, snooze, dismiss) and dispatch remediation actions (block tool, disable connector, escalate scanner) — mutations require explicit confirm=true
• Sessions
  • List recent sessions with filters (status, client, user, date range) and pagination
  • Get session details including events, tool calls, scan results, and AgentGuard findings
• Automation building blocks
  • Plugins: create/update, manage connectors (tool allowlists) + attach skills
  • Skills: create/update skill instruction files used by plugins
  • Agents: manage agents; edit connectors and skills incrementally (set_agent_connectors / add_agent_connectors / remove_agent_connectors, set_agent_skills / add_agent_skills / remove_agent_skills); create schedules/webhooks; configure Slack DM mode; enable/disable memory; enable/disable agents; delete agents (delete_agent, owner or agent manager only, confirm-required). create_agent requires ai_provider_id and accepts optional model and icon parameters; update_agent covers metadata and settings such as is_disabled, and accepts ai_provider_id to move an agent to a different AI provider (pass it alongside model when the new model lives on a different provider).
  • Agent models: list available models for agents and update an agent’s model
  • Subagents: add, update, and delete subagents on an agent (confirm-required)
  • Artifacts: create standalone artifacts (files) from text or base64 content; requires artifacts feature flag and confirm=true (confirm-required)

---

​

Getting started

---

​

Example prompts (copy/paste)

​

Analytics (adoption + usage)

• “Use Runlayer MCP to export top tools used in the last 30 days as CSV, then summarize the top 10 and call out failure rate.”
• “Export tool calls hourly for the last 7 days (UTC) and describe the daily pattern.”
• “Which MCP clients (Cursor/Claude/etc) generated the most MCP activity last month? Export CSV and rank them.”

​

Audit logs (investigations)

• “Use Runlayer MCP to list recent tool_call_failure audit logs. Group by server name and show the most common error messages.”
• “Find audit logs with correlation_id=<id> and summarize the sequence of events.”
• “For the most recent policy denied events, show actor + server + tool and the violation reason.”
• “Export the last 30 days of security violation audit logs as CSV and identify the top offending tools.”

​

Incidents + sessions

• “Use Runlayer MCP to list open incidents from the last 7 days and summarize by source type.”
• “Get the details of the highest-priority incident and show the available remediation actions.”
• “List sessions for user@company.com from the last 24 hours and flag any with security violations.”

​

Inventory + debugging

• “List servers I can access, then for the Slack server list its tools and give me the install link for Cursor.”
• “I think a connector is missing tools. List the server tools via Runlayer MCP and compare to what the UI shows.”

---

​

Notes and gotchas

• Admin-only vs non-admin: some reporting and governance tools require admin access. Non-admins may see a reduced view (for example, audit logs are limited to the caller unless you are an admin).
• Safe-by-default mutations: tools that change state require an explicit confirm=true parameter. If your assistant asks to “confirm”, that is expected.
• Large outputs: some audit log entries can be huge. Listing tools may omit large fields; fetch the specific record when you need the full payload.

---

​

Related resources