adk-revsec: RevSec for Google ADK
Ship ADK agents your customers' security teams will approve.
Agents built with the Google Agent Development Kit (ADK) take real actions: they refund orders, send emails, change
records and call MCP servers. RevSec decides, before each action runs, whether the agent is allowed to take it, and
keeps a record of what every agent did. Add one plugin to your ADK App; your agent code stays the same.
One plugin covers all three things an agent touches: its actions (Agent Security), the MCP servers it calls (MCP Governance) and what reaches its model (Model Security).
What it does for your business
- Stops risky actions before they happen. Each tool call is checked against your policies before it runs. A refund above a limit, a delete, or a call to an MCP server nobody approved is blocked, and the agent is told why, so it can answer the user instead of failing.
- Keeps prompt injection and leaked data away from your model. RevSec Model Security checks what users ask before it reaches the model, and what tools hand back (web pages, documents, MCP replies) before the model reads it, for instructions aimed at the model, secrets and personal data. Your organisation's own prompt rules apply too.
- Governs your MCP servers. Each MCP call is checked against that server: whether it is approved, its policies and its known vulnerabilities.
- Gives you one view of every agent. Each agent appears in your RevSec console with the models it uses, its tools and MCP servers, its risk rating, and its decisions grouped by conversation. Prompt and tool-result checks also show in Model Security.
- Proves control, action by action. Replay any session in Activity Explorer: what the user asked, each tool and MCP call, and what RevSec decided. Frameworks shows which controls in the EU AI Act, ISO/IEC 42001, NIST AI RMF, SOC 2 and more your policies are mapped to, and Evidence Packs gather the evidence for a customer's security review or auditor.
- Covers every agent in the App. Root agents and sub-agents are checked the same way, with no code in each agent.
Quick start
pip install "adk-revsec[mcp]"
Get a key from the RevSec console (Customer accounts → New key in a builder account, or Settings → SDK), then:
export REVSEC_API_KEY=rsk_...
export REVSEC_BASE_URL=https://app.revsec.app/fcc
from google.adk.agents import LlmAgent
from google.adk.apps import App
from google.adk.runners import Runner
from google.adk.sessions import InMemorySessionService
from adk_revsec import RevSecPlugin, revsec_mcp_toolset
def refund_order(order_id: str, amount: int) -> dict:
"""Refund an order."""
...
notes = revsec_mcp_toolset("notes", command="npx", args=["-y", "@acme/notes-mcp"])
agent = LlmAgent(
name="orders_agent",
model="gemini-flash-latest",
instruction="Help customers with their orders.",
tools=[refund_order, notes],
)
app = App(name="orders_app", root_agent=agent, plugins=[RevSecPlugin()])
runner = Runner(app=app, session_service=InMemorySessionService())
That's all. The first request registers the agent in RevSec. From then on its tool calls, prompts and tool results are checked, and the decisions show in the console.
What RevSec checks
| When | What | If RevSec stops it |
|---|---|---|
| Before the run | What the user asked | The model is never called and the request is not kept in the session; the user gets a short reply saying it was blocked |
| Before each tool call | The agent's own tools, against the agent's policies | The tool never runs; the model gets a response saying why |
| Before each MCP tool call | The call, against that MCP server: whether it is approved, its policies, its known vulnerabilities | The call never reaches the server; the model gets a response saying why |
| After each tool call | What the tool handed back | The model gets "withheld" instead of the content |
Blocked calls are recorded, and MCP calls record whether they succeeded or failed and how long they took.
MCP servers
Build each MCP toolset with revsec_mcp_toolset(name, ...) so RevSec checks its calls against that server:
github = revsec_mcp_toolset("github", url="https://api.githubcopilot.com/mcp/")
notes = revsec_mcp_toolset("notes", command="npx", args=["-y", "@acme/notes-mcp"])
An McpToolset you build yourself works too: note_mcp_server(toolset, "github"). RevSec never sends the launch
command's other arguments, which can carry tokens.
Options
RevSecPlugin(
agent_name="orders-desk", # default: the root agent's name
customer_facing=True, # shown on the agent and used in its risk rating
description="Handles order questions and refunds",
owner_email="team@example.com",
environment="production",
on_block="message", # or "raise" to stop the run instead
)
With on_block="raise", ADK stops the run with its RuntimeError, and revsec.RevsecBlocked is its cause.
If RevSec can't be reached, calls go ahead by default, so an outage never stops your product. To block them instead:
import revsec
revsec.mcp.configure(api_key="rsk_...", base_url="https://app.revsec.app/fcc", failure_mode="fail_closed")
If your model calls go through the RevSec AI gateway, the gateway already checks prompts, so turn that check off here:
import revsec
revsec.mcp.configure(check_prompts=False)
Requirements
- Python 3.11 or later, and Google ADK 1.18 or later (1.x and 2.x are both tested)
- A RevSec account: start a free 30-day trial, no card needed
Links
- RevSec: https://app.revsec.app/start?from=google-adk
- Source and issues: https://github.com/RevUp-AI/adk-revsec
- The RevSec Python SDK: https://pypi.org/project/revsec-sdk/
Licensed under Apache 2.0. RevSec is a product of RevUp AI LLC.
Metadata
Release files for adk-revsec 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| adk_revsec-0.1.0.tar.gz | 23.3 kB | Without provenance | Details for adk_revsec-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| adk_revsec-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for adk_revsec-0.1.0-py3-none-any.whl |
Total release size: 39.7 kB
Release files / adk_revsec-0.1.0.tar.gz
| Download URL | adk_revsec-0.1.0.tar.gz |
|---|---|
| Size | 23.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f0f2cb194dd3297b8400b400b8ba54af5547ecbd97c2941705740bb6d0dff5b7
|
|
BLAKE2b-256 checksum How to use checksums |
f8e1a1595d93fabda4127eb0d1622fae196ecd7bae4d16d4954eea8c76654c61
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.0
|
Release files / adk_revsec-0.1.0-py3-none-any.whl
| Download URL | adk_revsec-0.1.0-py3-none-any.whl |
|---|---|
| Size | 16.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a75c86795a355a267769e2e14d86e76d3543772855ed7abcb7783d8f70dad2d3
|
|
BLAKE2b-256 checksum How to use checksums |
93250fde85b5b3dc50960b6f171dd729e0a884477b34235d5039d4b0b53ebe19
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.0
|
Security for adk-revsec 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.