Skip to main content
TrustGate publishes a merged MCP catalog to the agent and decides which tools it can reach at all. A TrustGuard policy on the application additionally inspects the content of that traffic. Read Microsoft Copilot Studio first if you have not decided between the two integration paths.

​
What it covers

This path sits on the agent’s MCP tool connection. TrustGate publishes one catalog and decides which of those tools the agent can reach. You can use this path on its own, or together with threat detection. Threat detection screens every tool the agent runs; this path governs the MCP tools TrustGate publishes. Redaction is available when a TrustGuard policy is attached: Transform rewrites inspected text on DLP outcomes. Non-text image, audio, or resource blocks are not inspected. The Tool Injection policy applies only to LLM traffic and does not affect MCP.

​
Before you start

Do not configure client credentials manually. TrustGate publishes OAuth metadata and supports Dynamic Client Registration, so Copilot Studio registers itself. If Copilot Studio asks for a Client ID or Client secret, confirm that authentication is set to Dynamic discovery and that the server URL is the endpoint copied from Connect.
1

Create the MCP application

In Agent Gateway → Access → Applications, create an application and add the servers and toolkit you want the agent to have on General — its type follows from that. Set Auth to the identity provider Copilot Studio signs in through, then copy the URL from the Connect tab:
Authentication options. The Copilot Studio configuration is the same for both options; only the application configuration changes.Every caller an application admits sees the same registries and toolkit. When different people should see different tools, create one application per tool set, or let people self-serve from the MCP Store governed by Access.
2

Add the MCP tool in Copilot Studio

  1. Create a tool → MCP.
  2. Set Authentication → OAuth → Dynamic discovery.
  3. Paste the application URL from step 1 as the server URL. Leave the defaults. If Power Automate opens, no changes are needed there.
3

Build the agent and activate the connection

  1. Create an agent and add the MCP Server tool from step 2.
  2. On the first run, activate every connection when prompted, including the MCP Server itself.
  3. Complete the NeuralTrust or IdP login if prompted. If an upstream registry uses OAuth (forwarded) and the user has not connected it, the first tool call returns a connection link. After authorization, TrustGate stores and refreshes the credential.
4

Verify

  1. Submit a request that invokes a tool from a bound registry.
  2. Confirm the agent lists only the tools granted by the application’s toolkit.
  3. Confirm the call in TrustGate Activity.

​
Optional: inspect tool calls and results

The preceding steps configure an access-only connection. To evaluate the content of MCP traffic with TrustGuard:
  1. Follow the TrustGate integration to create a TrustGate collector and assign a TrustGuard runtime policy. Add Input rules for tool calls and Output rules for tool results. Start in Observe mode.
  2. In Agent Gateway → Policies → Catalog, add TrustGuard. Select the collector, set direction to request_response, and target the Copilot Studio application. Keep the guardrail in Observe while testing.
  3. Invoke a tool and confirm the input and output decisions in TrustGuard Activity.
  4. After reviewing the decisions, switch the runtime policy and guardrail to Enforce.
In Observe mode, findings are recorded without blocking or rewriting traffic. If a transform cannot be applied safely in Enforce mode, TrustGate blocks instead of forwarding unmasked content. Redaction applies to DLP outcomes only.

​
Reference

​
Configuration

MCP endpoint. Each MCP application has a streamable-http endpoint. The agent receives the merged catalog from the registries assigned to that application:
The slug is the first path segment on the application’s proxy URL, and the path must end in /mcp. Copy the URL from the Connect tab instead of assembling it manually. Agent authentication. TrustGate acts as an OAuth2 authorization server for connecting agents and supports Dynamic discovery: The application configuration determines which IdP handles the login. See Auth. Upstream authentication is separate. Authenticating Copilot Studio to TrustGate is not the same as authenticating TrustGate to the MCP servers behind it. Configure the latter with mcp_target.auth.mode on the registry: none, static, client_credentials, passthrough, exchange or forwarded. forwarded requires the user to provide consent on first use. Tool names. Unique names pass through unchanged; a collision is prefixed with the registry name (asana_create_task). Use the name shown to the agent when configuring tool restrictions. Fail mode. fail_mode on the application decides what happens when an upstream server is unavailable. open skips the failed server; closed fails the call. For role-based applications the effective mode is open only when every contributing role declares it open.

​
Troubleshooting