TotalHealAgentGate

How it works

1. RegisterAdd your MCP servers; AgentGate reads their tools and keeps their credentials.
2. IdentifyGive each agent its own token, an owner and the tools it may use.
3. CheckEach call is checked against the allow list and, on Professional, for sensitive data and approval.
4. ApproveA person approves or rejects high-impact calls; the approved call goes through once.
5. RecordEvery call is recorded; unusual behaviour raises an alert and the kill switch stops agents at once.

Reference architecture

Key capabilities

• Registry of MCP serversRegister each server’s endpoint once; AgentGate reads its tools and how each declares itself (read only, or changes and deletes data). Turn any tool off for everyone, and pause a whole server.
• Credentials agents never holdThe server’s token is kept encrypted by AgentGate and added to each forwarded request. Agents authenticate to AgentGate with their own token; revoking it cuts the agent off without touching the server.
• An identity per agentEvery agent has a name, an accountable owner, a token shown once (only its fingerprint is kept) and an allow list of servers and tools. When an agent lists tools it sees only the ones it may call.
• Arguments checked for sensitive dataBefore a call is forwarded its arguments are inspected with the DataShield detectors — Aadhaar, PAN, bank accounts and IFSC, card numbers, cloud keys and passwords — and stopped at the threshold you set per server, with a message the agent can act on.
• A person approves what mattersTools that change or delete data can require approval. The call waits; a person approves or rejects it in the console with a note, and that exact call — same tool, same arguments — goes through once within 15 minutes. An AI agent can never approve.
• Rate limits and a kill switchEach agent has its own limit of tool calls a minute. Disable one agent, or stop every agent at once, and requests are refused immediately.
• Unusual behaviourAfter a learning week, an agent that calls a tool it has never used, or makes three times more calls in an hour than its busiest hour so far, raises an alert in the same incident queue as everything else.
• A record of every callAgent, server, tool, decision and reason, argument names and sizes (never their values), sensitive data found (masked), result and latency — for audits and for investigating what an agent did.

In the console

Deployment options

System requirements

Technical specifications