The gap in most AI agent security setups is not detection. It is the absence of a gate. By the time a monitoring tool flags a tool call, the call has already run, the data has already moved, and the action has already taken effect. Vaikora Guard MCP is an open-source proxy that sits inline and enforces policy before any tool call reaches the target.
It is MIT-licensed, written in Python, published on PyPI as `vaikora-guard-mcp`, and self-hostable. This post covers what it does, how the enforcement works, and how to wire it in.
The Problem With Post-Hoc Checks
An AI agent operating through the Model Context Protocol can call any tool the MCP server exposes: file writes, API calls, database queries, shell commands. Each call carries a tool name and a set of arguments. If your only control is a log review or an alert fired after the fact, you have visibility but not control.
What matters is the decision point. Can you inspect the call, evaluate it against a policy, and either allow, block, or modify it before execution? That is what a proxy gives you that a sidecar monitor does not.
What Vaikora Guard MCP Actually Does
The proxy intercepts every tool call that an MCP client sends to an MCP server. For each call, it runs the request through a policy evaluation pipeline before forwarding it. The result of that evaluation is one of four outcomes: allow, block, modify, or require approval. If the policy blocks the call, the tool never runs. If the policy requires approval, execution pauses until a human responds.
The enforcement is deterministic. Identical input always produces an identical decision. That is not a minor implementation detail. It means you can reason about what the system will do, write tests that confirm it, and produce an audit trail that is reproducible.
Every decision is written to a SHA-256 hash-chained, tamper-evident audit log. The chain gives you an ordered, verifiable record of every tool call evaluated, the policy outcome, and the timestamp.
A concrete example: an agent is asked to export customer records to an S3 bucket. The tool call arrives at the proxy carrying the bucket name and the data shape. A policy rule inspects the destination against a blocklist of unapproved external buckets. The call is blocked and the block is written to the audit chain before the agent sees any response from the tool.
Deployment and Configuration
Installation is a single pip command:
“`
pip install vaikora-guard-mcp
“`
Configuration is through a policy file that defines rules per tool name, per argument pattern, or across all calls. You can write allow rules, block rules, and approval-required rules. The proxy starts in front of any existing MCP server without touching the server’s implementation or the client’s SDK.
Enforcement latency at P50 is 8ms and at P99 is 45ms. For most agent workflows, this is not perceptible. For latency-sensitive pipelines, it is worth measuring under realistic load, since the proxy can handle more than 10,000 actions per second.
The proxy supports 12 LLM providers with no SDK migration required. If you are running Claude, GPT-4o, Gemini, or any of the other major hosted models, you do not need to change how the agent is built.
Compliance Presets
For teams operating under regulatory requirements, Vaikora Guard MCP ships presets for SOC 2, HIPAA, GDPR, PCI DSS, and ISO 27001. Each preset is a policy bundle that reflects the data handling and access control requirements of that framework. You can extend a preset with organization-specific rules or use it as a starting point.
What This Gives a Security Team
The audit chain is the part security teams care about most in practice. Compliance auditors ask two questions: what happened, and can you prove it? A hash-chained log where every entry is signed into the chain answers both. You can produce the record for any time window, verify its integrity, and show that no entry was removed or altered.
The enterprise control plane, hosted by Data443, extends this with centralized policy management, approval workflows, and SIEM integrations including Microsoft Sentinel, SentinelOne, and CrowdStrike Falcon. But the core proxy works without any of that if you want to self-host everything.
Where to Start
Pull the package from PyPI, review the policy schema in the repository, and run it against a test MCP server with a few representative tool calls. Check that your block rules fire correctly, then inspect the audit log to confirm the hash chain is intact. If you are running agents that touch sensitive data or external systems, that test sequence should take under an hour and will tell you exactly what your current policy gaps are.
The source is available on GitHub and the package is on PyPI under `vaikora-guard-mcp`.