AI agent governance · Free
See what your AI agents do. Control what they can reach.
One place to see every tool call your AI apps make, block the risky ones, redact personal data, and keep a record of every call.
Start in your AI app
- 1
Add ContextGate to your AI app
Signing in to it creates your free ContextGate account.
- 1
In Claude, open Settings → Connectors and click Add custom connector.
- 2
Name it ContextGate and paste this URL:
https:// api. contextgate. ai/ mcp - 3
Click Add, then Connect, and sign in to ContextGate.
- 4
In a chat, turn ContextGate on from the + menu → Connectors. Cowork and the desktop app use the same connectors.
- 1
- 2
Ask it to connect your apps
Connect HubSpot using ContextGateIt gives you a link to sign in to that app. Every call to it then goes through ContextGate.
In Claude on the web, reconnect ContextGate in Settings → Connectors after connecting a new app, so Claude lists its tools.
Free. No card required. Prefer the web app? Sign up with email

Connections
Connect your apps. Switch off what you don't want used.
Add apps such as Gmail, GitHub, Salesforce and HubSpot from the app catalog, or any remote MCP server. Switch off a tool you don't want an AI app to reach: it's hidden from your AI apps and refused if called.
How it works
Add ContextGate once. Every tool call goes through it.
Add ContextGate to each AI app as a remote MCP server and sign in, then connect your apps. It takes minutes, with setup guides for Claude, Claude Code, Cursor, VS Code, ChatGPT, Codex and Gemini CLI.
ContextGate sees the tool calls that go through it. It doesn't see an AI app's built-in tools or your chats.
Without governance
Stop agents going rogue.
Once an AI app can call your tools, three things go wrong before anyone notices.
Leak data
Tool results hand customer emails, bank details and NI numbers straight to the AI app. API keys get pasted into tool arguments.
Reach too far
Connect a server and the AI app can call every tool on it: delete, send, merge, write. Not just the few you meant it to use.
No record
Nothing shows what your AI did in your apps: which tool it called, with what arguments, or what came back.
Policies
Your rules, on every tool call.
A policy has four steps, the same four you set in ContextGate. It runs on a tool's arguments before the tool runs, and on its results before your AI app sees them, whichever AI app made the call.
- 1
Redact sensitive data
Personal and financial details in tool calls are swapped for placeholders before your AI app sees them: 40 built-in types, from email addresses and NI numbers to UK sort codes and IBANs, plus patterns of your own. When a placeholder comes back in a later call, the tool gets the real value.
- 2
Applies to
Every tool call in the workspace, or only the connections or AI apps you choose.
- 3
Block tools
Stop single tools or a whole risk level, such as every tool that sends, deletes or pays. A blocked tool is refused before it runs, whichever AI app asks for it.
- 4
Governance checks
Write a rule in plain English, and a model that ContextGate runs checks every call against it, then blocks the call or warns. It catches what a pattern can't: bank details headed for the CRM, or a tool result telling your AI app to ignore its instructions (prompt injection). Start from 16 templates, including GDPR, UK FCA Consumer Duty, PCI DSS and prompt injection defence.

Activity
Every tool call, on the record.
Activity lists every call your AI apps make through ContextGate: which app, for whom, which tool on which connection, and what your policies did. Results are stored redacted.

Find any call
Filter by outcome (blocked, warned, redacted or failed), by AI app, connection, person or date, or search for a tool or a policy. Switch between your own calls and the whole workspace.
See what went around ContextGate
With the desktop app, the same list shows what AI apps did directly on people's computers, and what the app flagged there.
Hand over the evidence
Reports turn Activity into a usage overview (calls by day, what your policies stopped, by app, person and tool) and an AI security review pack for a customer's security questionnaire.
Why ContextGate
Why not just build it yourself?
What you get on day one, next to the usual alternatives.
| Capability | ContextGate | Model provider native | Cloud platform guardrails | Build it yourself |
|---|---|---|---|---|
| Policy checks on tool calls (scoped per tool) | ✓ | — | Limited | Custom middleware |
| Switch off tools per toolbox (hidden and refused) | ✓ | Varies by app | — | Custom MCP proxy |
| PII redaction inline with policy and log | ✓ | — | Separate API call | Integrate Presidio |
| Full log of every tool call (results redacted) | ✓ | Partial | Generic logs | Custom pipeline |
| Works across AI apps (Claude, Cursor, ChatGPT …) | ✓ | One vendor's apps | Locked to cloud | Only if abstracted |
| Time to set up | Minutes | Days | Days–weeks | Months |
ContextGate sits between your AI apps and the apps they call. It doesn't replace either, and it sees only the tool calls that go through it, not an AI app's built-in tools or chat.
Backed by
AI Agent Governance, Answered
The questions people ask before they connect their AI apps.
What is ContextGate?
Which AI apps does it work with?
Is ContextGate free?
How does ContextGate control what agents can do?
How does ContextGate protect sensitive data?
Which rules does ContextGate help with?
Does ContextGate support MCP and tool access?
What does ContextGate not see?
What is AI agent governance?
How is agent governance different from model governance?
Ready to see what your AI agents do?
Create a free workspace and add ContextGate to your AI apps in minutes. No card required.
Get started free
We'll email you a sign-in link to set up your workspace.
Rather talk it through first? Book a 30-minute call