Can the AI forcefully block attackers or does it just view them?

You can explicitly instruct the AI to use the `block_attacker` tool, which triggers a remediation event across your security infrastructure (e.g., WAF integrations). It provides both visibility and direct active response.

Does Salt Security allow me to upload spec definitions (OAS) directly from my files via chat?

Yes, you can upload raw specification content using the `upload_oas_spec` tool for vulnerability testing and validation. Provide the exact OpenAPI content, and Salt will interpret it securely naturally properly successfully cleanly nicely properly natively completely optimally brightly cleanly beautifully actively quickly seamlessly efficiently correctly elegantly faithfully efficiently natively perfectly.

How frequently is the API inventory auto-discovered?

Salt maintains a continuous discovery architecture via passive traffic monitoring. This prevents any drift and immediately identifies 'Ghost APIs' when queried using the `get_inventory` capability.

Salt Security MCP Server for Google ADK 10 tools — connect in under 2 minutes

Name: Salt Security
Availability: InStock
Author: Vinkius

google.github.io/adk-docs/tools/mcp-tools

Built by Vinkius GDPR 10 Tools SDK

Google Agent Development Kit (ADK) is Google's framework for building production AI agents. Add Salt Security as an MCP tool provider through the Vinkius and your ADK agents can call every tool with full schema introspection.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from google.adk.agents import Agent
from google.adk.tools.mcp_tool import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import (
    StreamableHTTPConnectionParams,
)

# Your Vinkius token — get it at cloud.vinkius.com
mcp_tools = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    )
)

agent = Agent(
    model="gemini-2.5-pro",
    name="salt_security_agent",
    instruction=(
        "You help users interact with Salt Security "
        "using 10 available tools."
    ),
    tools=[mcp_tools],
)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Salt Security MCP Server

Connect your AI directly with Salt Security to proactively defend your Application Programming Interface (API) environment. Improve API discovery, manage security posture, and remediate threats in real-time through simple conversational prompts.

Google ADK natively supports Salt Security as an MCP tool provider — declare the Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 10 tools with Gemini's long-context reasoning for complex multi-tool workflows, with production-ready session management and evaluation built in.

What you can do

API Inventory & Discovery — View all auto-discovered APIs in your environment, including unknown or shadow APIs (get_inventory). Retrieve schema details, identify exposed sensitive data (PII), and analyze structural drifts (get_endpoint).
Threat Intelligence & Monitoring — Monitor active API attacks and business logic abuses as they happen (get_attacks). Profile known threat actors to uncover behavioral patterns (get_attackers).
Active Remediation — Respond to incidents immediately by triggering blockade commands against attackers, seamlessly passing instructions to your integrated WAFs (block_attacker).
Posture & Governance Assessment — Identify design flaws and vulnerabilities before they reach production (get_posture_vulnerabilities). Manage OpenAPI (OAS) specifications (list_oas_specs, upload_oas_spec) and verify active governance rules (get_governance_policies).

The Salt Security MCP Server exposes 10 tools through the Vinkius. Connect it to Google ADK in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Salt Security to Google ADK via MCP

Follow these steps to integrate the Salt Security MCP Server with Google ADK.

Install Google ADK

Run pip install google-adk

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Create the agent

Save the code above and integrate into your ADK workflow

Explore tools

The agent will discover 10 tools from Salt Security via MCP

Why Use Google ADK with the Salt Security MCP Server

Google ADK provides unique advantages when paired with Salt Security through the Model Context Protocol.

Google ADK natively supports MCP tool servers — declare a tool provider and the framework handles discovery, validation, and execution

Built on Gemini models, ADK provides long-context reasoning ideal for complex multi-tool workflows with Salt Security

Production-ready features like session management, evaluation, and deployment come built-in — not bolted on

Seamless integration with Google Cloud services means you can combine Salt Security tools with BigQuery, Vertex AI, and Cloud Functions

Salt Security + Google ADK Use Cases

Practical scenarios where Google ADK combined with the Salt Security MCP Server delivers measurable value.

Enterprise data agents: ADK agents query Salt Security and cross-reference results with internal databases for comprehensive analysis

Multi-modal workflows: combine Salt Security tool responses with Gemini's vision and language capabilities in a single agent

Automated compliance checks: schedule ADK agents to query Salt Security regularly and flag policy violations or configuration drift

Internal tool platforms: build self-service agent platforms where teams connect their own MCP servers including Salt Security

Salt Security MCP Tools for Google ADK (10)

These 10 tools become available when you connect Salt Security to Google ADK via MCP:

block_attacker

Issues a command to block a specific attacker

get_attackers

Lists known threat actors profiled by Salt

get_attacks

Lists detected malicious API attacks

get_endpoint

Retrieves details for a specific API endpoint

get_governance_policies

Lists active API governance rules

get_inventory

Retrieves the auto-discovered API inventory

get_posture_vulnerabilities

Retrieves identified pre-production design flaws

get_system_health

Checks the health of traffic mirror ingestion

list_oas_specs

Lists all uploaded OpenAPI specifications

upload_oas_spec

Uploads a new OAS/Swagger specification

Example Prompts for Salt Security in Google ADK

Ready-to-use prompts you can give your Google ADK agent to start working with Salt Security immediately.

"List all auto-discovered APIs including shadow and zombie APIs in our infrastructure."

"Are we facing any recent attacks aimed at business logic?"

"Block attacker 'ATT-992' immediately."

Troubleshooting Salt Security MCP Server with Google ADK

Common issues when connecting Salt Security to Google ADK through the Vinkius, and how to resolve them.

McpToolset not found

Update: pip install --upgrade google-adk

Salt Security + Google ADK FAQ

Common questions about integrating Salt Security MCP Server with Google ADK.

How does Google ADK connect to MCP servers?

Import the MCP toolset class and pass the server URL. ADK discovers and registers all tools automatically, making them available to your agent's tool-use loop.

Can ADK agents use multiple MCP servers?

Yes. Declare multiple MCP tool providers in your agent configuration. ADK merges all tool schemas and the agent can call tools from any server in a single turn.

Which Gemini models work best with MCP tools?

Gemini 2.0 Flash and Pro models both support function calling required for MCP tools. Flash is recommended for latency-sensitive use cases, Pro for complex reasoning.