Runlayer Plugin

Documentation Index

Fetch the complete documentation index at: https://docs.runlayer.com/llms.txt

Use this file to discover all available pages before exploring further.

​

What Runlayer Plugin Includes

• active hosted connectors the user can access through policies
• accessible Runlayer skills
• Runlayer platform tools exposed through the Runlayer MCP connector

• local connectors that run on a user’s machine
• draft or disabled connectors as normal executable tools
• connectors blocked by policy for that user
• tools the user could not use through the underlying connector directly

​

Why teams use it

• admins can standardize the MCP experience across teams
• users get a simpler setup and fewer things to configure
• models can search for the right tool when needed instead of carrying every tool definition in context
• Runlayer policies, approvals, OAuth checks, ToolGuard, and audit logs stay in the loop

​

How tool discovery works

1. The model calls search_tools with the task it wants to accomplish.
2. Runlayer Plugin searches across the user’s accessible connectors and returns relevant tool definitions.
3. The model calls execute_tool with the exact returned tool name and arguments.
4. Runlayer routes the call to the underlying connector and applies the same policy, security, auth, and audit controls as a direct connector call.

​

search_tools

{
  "meta": "Need to create a GitHub issue for the deployment bug",
  "query": "create GitHub issue",
  "top_k": 5
}

​

execute_tool

{
  "meta": "Create the issue the user requested",
  "tool_name": "github_create_issue",
  "arguments": {
    "repo": "acme/app",
    "title": "Deployment bug",
    "body": "Deployment failed after the latest release."
  }
}

​

Skills and /runlayer

• use Runlayer Plugin as the default entrypoint for tools, plugins, and skills
• call search_tools before execute_tool
• avoid guessing tool names
• route external tool calls through Runlayer so security policies and audit logs remain in effect

​

Permissions and security

• User-scoped results: each user sees only hosted connectors and skills they can access.
• Policy-aware discovery: policy changes affect what appears in Runlayer Plugin on the next request.
• Normal execution path: execute_tool delegates to the underlying connector proxy, so PBAC, ToolGuard, OAuth/session checks, and audit logging still apply.
• OAuth preserved: if a connector needs user authorization, Runlayer Plugin can surface an auth-required tool instead of silently hiding the connector.
• Partial results: if one connector is slow or temporarily unavailable, Runlayer Plugin can still return tools from other available connectors.

​

Admin rollout options

​

Anthropic org install

• runlayer/.claude-plugin/plugin.json
• runlayer/.mcp.json
• runlayer/skills/runlayer/SKILL.md

1

Download runlayer.zip

In Runlayer, open the Runlayer Plugin page, click Add to Organization, select Anthropic, and click Download zip.

2

Open Claude admin plugin settings

Go to Claude admin plugin settings and click Add plugin.

3

Select Upload a file

Choose Upload a file.

4

Upload the zip

Select runlayer.zip and click Upload.

5

Require access

Change user access to Required.

​

OpenAI org install

• runlayer/SKILL.md
• runlayer/agents/openai.yaml
• runlayer/assets/runlayer-logo.svg

​

User examples

• “Use Runlayer to find the right GitHub tool and create an issue for this bug.”
• “Search for Slack tools I can use, then summarize messages about the incident.”
• “Use /runlayer to list available skills for release management.”
• “Find the Salesforce tool for reading account details, then look up Acme.”

Search Runlayer Plugin for the tool you need before executing anything. Use the exact tool name from search results.

​

Troubleshooting

​

Related docs