Connect Gem to Claude
Give Claude governed access to Gem’s 15 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Gem to Claude in four steps
Admins approve the server once. Everyone in Claude then gets it through the same governed connection.
- 1
Add Gem to Runlayer
Gem isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect Claude to Runlayer
Admins install the Runlayer Plugin for everyone from Claude’s admin plugin settings, or users add it themselves. With direct tool listing turned on for your deployment, Gem’s 15 tools show up in Claude’s own tool list.
Claude setup guide - 3
Sign in to Gem
Sign in the way Gem requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Gem from Claude
Gem’s approved tools appear in Claude. Every call is checked against policy and recorded.
Tools
15 Gem tools in Claude
Runlayer policy decides which of these Claude users can call.
Get application
Look up one application (a candidate on a specific job) by ext_id — status, stage, stage_entry, gem_status (the Talent Pipeline's computed next-step status and SLA health, e.g. NEEDS_DECISION /…
Get job
Look up one job by ext_id — title, status, requisition id, ATS, department/office, and link.
Get metrics catalog
List the metrics and dimensions this team can report on with query_metrics.
Get person
Look up one candidate by ext_id — name, current title, company, school, emails, phone numbers, and links, plus optional fields (full work history, education, custom fields, applications, activity…
Get project
Look up one project by ext_id — name, description, owner, link, type, privacy, archived status, and people_count (candidates in the project).
Get saved report
Look up one saved analytics report (Pipeline Analytics or Outreach) by ext_id — its name, type, owner, link, and a ready-to-run query_metrics payload translated from the report's saved configuration.
Get sequence
Look up one outreach sequence by ext_id — name, status, whether it is a reusable template (is_template) and whether it is archived (is_archived), owner, link, a version (the sequence's edit version —…
Get sequence tokens
List the merge tokens available for writing a sequence stage's subject or body on this team.
Control
What Runlayer can see and stop in Claude
Some controls apply to every client at the gateway. Others depend on what Claude exposes to Runlayer.
Gateway policy (available)
Every Gem call from Claude passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Claude as the client, the tool, and the policy and scanner decisions.
Anthropic inference hooks (available)
With Claude Enterprise, Anthropic sends each governed Claude prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).
Compliance API import (available)
Anthropic Compliance API imports Claude web and desktop chats for review.
Managed browser extension (available)
Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.
Stop a call before it runs (available)
Runlayer can reject a Claude prompt before Anthropic runs it, which stops the whole request rather than one tool call.
Block output after it runs (available)
Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.
Redact output in place (not available)
Anthropic Inference hooks cannot return a rewritten prompt, so Runlayer cannot mask content in Claude. The gateway still applies policy to the call.
Frequently asked questions
Connect more