Let your Vertex AI agents do only the work you allow on Google Cloud.
Vertex AI agents reach your company systems through OpenAPI tools, Cloud Functions and Gemini. AvertGate sits in front of those calls and keeps the agent inside your IAM roles.


Works in front of the tools Vertex AI agents already connect to
See everything your Vertex AI agents do on one screen.
Agents built with Agent Builder, Search and Conversation apps and direct Gemini calls are gathered in one record stream.
- Every tool call recorded with its arguments
- Separate rules and records for each agent
- You show auditors records, not screenshots
- Product catalog searchedSearch data storeInstant
- Customer record readCloud Functions toolInstant
- Role assignment to a service account requestedWaiting for manager approvalIn Slack
- Storage bucket deletion requestedStopped by policyStopped
Give the agent just enough IAM role for its job.
Role assignment, key creation and resource deletion calls made with the agent’s service account are bound to your rules. Reads stay free; steps that raise privilege go to approval.
- Rules per tool and per argument
- Privilege-raising steps go to a manager
- A tool that is not listed does not run
The content the agent reads is under control too.
Documents and web pages retrieved by Search and Conversation can carry hidden instructions. AvertGate scans the result before the agent reads it.
- Hidden instructions are flagged in the content
- Suspicious sessions are tracked and repeats prevented
- Every finding goes on record
AvertGateAPP14:02
A Vertex agent wants to assign a role to a service account.
- Account[email protected]
- ReasonHidden instruction in a document
Waiting for approval. If rejected, the role is not assigned.
- ~4.2 msAverage added latency
- 100%Local isolation: data stays on your network
- ZeroChanges to agent code
Frequently asked
Does it work with Vertex AI Agent Builder?
The OpenAPI and Cloud Functions endpoints the agent calls as tools go through AvertGate. The agent keeps calling the same tools; only the connection address changes.
Is our data sent to AvertGate?
No. The gateway runs on your network. Tool arguments, results and file contents never leave it; only redacted event data reaches the dashboard.
Do we have to change agent code?
No. The agent connects to AvertGate instead of the tool server; only the connection address changes. If the tool call path runs over MCP or HTTP, the same policy applies.
Take your agents to production with confidence.
Every rollout starts with a demo and a POC on your own agents.



