Skip to main content
Claude Enterprise provides organization-managed access to Anthropic’s AI assistant. Administrators can connect TrustGuard to Anthropic’s inference hook to evaluate model requests, and add TrustGate as an organization connector to control access to MCP tools across claude.ai, Desktop, Cowork, and Claude Code. These integrations run through Anthropic’s cloud and do not require a local plugin. To evaluate individual commands and tool executions on a developer’s machine, use the Claude Code integration.

​
NeuralTrust controls

​
Deployment options

You can use either integration independently. Configuring the inference hook does not register an MCP connector or install Claude Code lifecycle hooks.
Use separate credentials for TrustGuard and TrustGate. TrustGuard uses a tgk_… collector key in the inference-hook Authorization header. Organization connectors authenticate MCP consumers with OAuth2. A tgk_… key does not authenticate MCP.

​
Before you start

Create the policy in Observe mode. Observe records decisions in Activity without enforcing them. Review the results, then switch the policy to Enforce. See Policies.
Users do not need NeuralTrust accounts for the inference hook. With an organization connector, each member completes an OAuth login against the IdP configured for the consumer, which may be NeuralTrust.

​
Inference hook

Anthropic’s organization-level Inference Hooks call TrustGuard before the model answers. The hook applies across Claude surfaces, requires no laptop installation, and cannot be disabled by end users. Each Anthropic organization endpoint maps to one TrustGuard collector. TrustGuard records the originating surface in source.application; see Attributes. The verdict is binary: allow or deny. There is no Ask dialog, masking, or visibility into individual tool executions on this path. It sees the model request, not the command Claude Code is about to run. Data Loss Prevention therefore blocks or reports here; it cannot mask in flight.
  1. In the Anthropic admin console, open Data and Privacy → Inference hooks.
  2. Set Hook URL to {TRUSTGUARD_BASE_URL}/v1/evaluate/claude and Authorization to Bearer <collector API key>. Use the tgk_… key, not a tgcol_… key.
  3. Save the endpoint in Anthropic. Saving is what generates the whsec_… signing secret.
  4. Paste whsec_… into the collector’s Connection tab in TrustGuard.
  5. Back in Anthropic, reopen Edit and run Test connection. The test fails until the secret has been added to TrustGuard.
  6. Assign a default policy to the collector before enforcing in production.
This integration installs no Claude Code lifecycle hooks. For control over individual actions on a developer machine, add the Claude Code plugin as well.

​
Organization connectors

Add TrustGate to Claude as an organization connector. The connector is available in claude.ai, Desktop, Cowork, and Claude Code. Claude receives the merged toolkit assigned to the MCP consumer. Copy the URL from the consumer’s Connect tab:
  1. As Owner, open Organization settings → Connectors → Add → Custom → Web.
  2. Set Name to TrustGate and URL to the Connect endpoint above.
  3. Save. Each member then opens Customize → Connectors → TrustGate → Connect and completes OAuth.
See Anthropic’s custom connectors guide.
The connector is called from Anthropic’s cloud, not from the user’s machine. The MCP URL must be reachable from the public internet, or from allowlisted Anthropic egress. A Hybrid-only MCP endpoint needs a public path or one of TrustGate’s private-network options before the connector can connect.
Prefer OAuth2 (or Use NeuralTrust): organization connectors expect OAuth. API-key consumers work through the Claude Code CLI instead. Claude Code loads the organization connector after the user completes the connection. Confirm in /mcp that TrustGate is the org connector, not “Provided by a plugin”. A local claude mcp add entry does not replace the organization connector.

​
Verify

​
Inference hook

  1. Run Test connection in Anthropic. It arrives in Activity with the collector’s connection-test event.
  2. Send a prompt from claude.ai and confirm the event with source.application = claude-ai.

​
Organization connector

  1. claude.ai or Desktop: Connectors → TrustGate shows connected, and its tools are available in chat.
  2. Claude Code: /mcp lists TrustGate; call a tool from a bound registry.
  3. Confirm the call in TrustGate telemetry. See Metrics.

​
Reference

​
Coverage

The following table describes the TrustGuard inference hook, not the TrustGate organization connector. ⚠️ Tool content is visible in the transcript and can be blocked, but only by blocking the whole inference at the single pre-inference decision point. There is no per-tool verdict. Use the Claude Code plugin to evaluate specific shell commands and MCP calls on managed developer machines. Neither integration evaluates model responses. Ask. The inference-hook endpoint has no approval dialog. An ask verdict becomes allowed. Use a Block gate when the request must be denied. Limits. The inference hook does not support redaction. There is no hook for assistant output, so model responses, system prompts, token usage, and extended thinking are not evaluated. A non-2xx response from TrustGuard is a delivery failure, not a deny. Anthropic’s failure handling then applies, while TrustGuard-side failures allow the request.

​
What is evaluated

The inference hook has one decision point before the model answers:
This is not the generic POST /v1/evaluate path. The inference-hook endpoint returns only allow or deny.

​
Configuration

Inference-hook ownership. An Anthropic organization administrator manages the hook URL and Bearer tgk_… header, then copies the whsec_… signing secret to the collector’s Connection tab in TrustGuard. Connector ownership. An Anthropic organization owner adds the MCP consumer’s Connect URL to the organization. Each member then completes OAuth. MCP auth. Organization connectors use OAuth2 (or Use NeuralTrust). Which IdP backs the login is configured on the consumer. See Auth. Authenticating to TrustGate is separate from authenticating to the upstream servers; a registry using OAuth (forwarded) returns a connect link on the first call for a user without a stored credential. For API-key authentication and private-data-plane headers through the CLI, see Claude Code. Configure the consumer’s available tools under Routing in the NeuralTrust console, or through a role for Identity-based consumers. To limit MCP tool calls, attach the Per-Tool Rate Limiter policy.

​
Attributes

Inference-hook deliveries carry collector.type = anthropic_inference_hook, model.provider = anthropic, and consumer.id from the actor’s email or id. The surface arrives in source.application: TrustGuard copies the frame’s source.application into the gate attribute map on every delivery. Unknown values are accepted as-is (open string). The local Claude Code plugin uses claude-code-plugin, not claude-code, and provides a per-developer consumer_id. The collectors use different values, so configure their gates separately. Use a collector and default policy for each integration path. Within Claude Enterprise, use a gate on source.application to apply different rules to each surface (Policies → Gates → Source application): For a gate targeting only the laptop plugin, use source.application eq claude-code-plugin with Ask or Block in its separate policy. See Claude Code attributes. Gates run before detectors. In Observe policy mode, Block is recorded but not enforced. Test the condition on the policy Test tab with Extra parameter Source application set to the surface you care about.

​
Troubleshooting