Connect Clay to GitHub Copilot CLI
Give GitHub Copilot CLI governed access to Clay’s 21 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Clay to GitHub Copilot CLI in four steps
Admins approve the server once. Everyone in GitHub Copilot CLI then gets it through the same governed connection.
- 1
Approve Clay in Runlayer
Add Clay from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect GitHub Copilot CLI to Runlayer
Users add the Runlayer Plugin to GitHub Copilot CLI by following Runlayer’s setup guide. GitHub Copilot CLI reaches Clay’s 21 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
GitHub Copilot CLI setup guide - 3
Sign in to Clay
Sign in the way Clay requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Clay from GitHub Copilot CLI
Clay’s approved tools appear in GitHub Copilot CLI. Every call is checked against policy and recorded.
Tools
21 Clay tools in GitHub Copilot CLI
Runlayer policy decides which of these GitHub Copilot CLI users can call. 12 read data only and 3 can change or delete data.
Add company data points
Add data points to companies in an existing search.
Add contact data points
Add data points to contacts in an existing search.
Ask question about accounts
Ask a natural language question about one or more accounts available in Clay Audiences.
Find and enrich company
Find and enrich a single company by domain or LinkedIn URL.
Find and enrich contacts at company
Search for contacts at a company by role, title, name, or department.
Find and enrich list of contacts
Find and enrich specific named contacts at their companies.
Get credits available
Check if credits are available for the workspace.
Get current workspace
Report which Clay workspace this connection is pinned to.
Control
What Runlayer can see and stop in GitHub Copilot CLI
Some controls apply to every client at the gateway. Others depend on what GitHub Copilot CLI exposes to Runlayer.
Gateway policy (available)
Every Clay call from GitHub Copilot CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, GitHub Copilot CLI as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call or permission request before GitHub Copilot CLI runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before GitHub Copilot CLI’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a successful tool’s output in GitHub Copilot CLI and pass the rest through.
In GitHub Copilot CLI
- When a tool fails, Runlayer records the error but cannot replace it.
Frequently asked questions
Connect more