Google ADK

Google ADK Agents run before_model_callback and after_model_callback around every model invocation. Dome uses these callbacks to scan inputs and outputs with Guardrails. Generate both callbacks from one Dome instance to add protection in a few lines.

Install

pip install "vijil-dome[local]" google-adk

See Install Dome for the full list of extras. Use vijil-dome[trust-adapters] instead when you also want identity and tool access control through Trust Runtime.

Guard an Agent

from google.adk.agents import Agent

from vijil_dome import Dome
from vijil_dome.integrations.adk import (
    generate_adk_input_callback,
    generate_adk_output_callback,
)

dome = Dome()

guard_input = generate_adk_input_callback(dome)
guard_output = generate_adk_output_callback(dome)

my_agent = Agent(
    model="gemini-2.0-flash-001",
    name="my_agent",
    description="An Agent built with Google ADK and protected by Dome",
    instruction="You are a friendly, question-answering AI Agent.",
    before_model_callback=guard_input,
    after_model_callback=guard_output,
)

Both generators accept two optional arguments:

Argument	Purpose
`blocked_message`	Replaces the default message returned when a Guard blocks
`additional_callback`	Your own callback, run alongside the Dome callback

guard_input = generate_adk_input_callback(
    dome,
    blocked_message="I cannot help with that request.",
    additional_callback=my_own_before_model_callback,
)

Dome is asynchronous internally and ADK does not yet support asynchronous model callbacks. Apply nest_asyncio before you build the Agent if you hit a nested event loop error.

Add the Full Trust Stack

secure_agent() adds identity, constraints, tool-level access control, attestation, and audit events to the content Guards. It modifies the ADK Agent in place:

from vijil_dome import secure_agent

secure_agent(my_agent, agent_id="travel-agent", mode="enforce")

See Trust Runtime for constraint sources and enforcement modes.

Deploy to Cloud Run

Follow the ADK Cloud Run deployment guide with the gcloud CLI, and add vijil-dome to your Agent’s requirements.txt. Request a container large enough for the Detector models, such as --cpu=4 --memory=8Gi.

Deploying through the ADK CLI is not supported, because it provides no way to declare extra requirements or increase the container size. Its default of 1 CPU and 512 MB is not enough for Dome’s default configuration.

The annoy package that backs the embeddings extra is not compatible with ADK Agents on Cloud Run. Use the default in-memory option when you need embeddings-based Detectors there.

Get Started

Evaluate Agents

Red Team

Protect Agents

Reference

Install

Guard an Agent

Add the Full Trust Stack

Deploy to Cloud Run

Next Steps

Configure Guardrails

Trust Runtime

​Install

​Guard an Agent

​Add the Full Trust Stack

​Deploy to Cloud Run

​Next Steps

Configure Guardrails

Trust Runtime

Install

Guard an Agent

Add the Full Trust Stack

Deploy to Cloud Run

Next Steps