Skip to main content
Glama

⚡ DROS™ VajraClaw (Hacker Edition)

Free Standalone Docker Governance Gateway for Multi-Agent Ecosystems (W3C DID & <1μs Fusing)

Official Website Docker Ready License: Free for Individuals U.S. Patent Pending RFC-010 Standard

English | 繁體中文說明 | 🌐 Official Website

DROS VajraClaw Hacker Edition is the official standalone, free Docker governance gateway designed for individual developers, AI researchers, and local developer workstations. It physicalizes execution security between autonomous AI Agents (Google Antigravity, Anthropic Claude, OpenAI Codex, Cursor, CrewAI, AutoGen, DeepSeek Harness) and your local operating system.


🛑 Why Deterministic Execution Governance?

Probabilistic security relying on Prompt Engineering, Llama-Guard, or LLM-as-a-judge inevitably fails at runtime:

  • Prompt Injections & Jailbreaks Bypass Text Guards: Attackers easily obfuscate prompts to trick agents into running rm -rf / or leaking .env secrets.

  • Unpredictable Latency & TOCTOU: Calling secondary models adds 1~3s delays and fails to protect OS syscalls.

  • Lack of Auditability: You cannot mathematically prove why an LLM wrapper allowed an action.

DROS is NOT a prompt wrapper; it is a Deterministic Runtime OS: It moves intelligence to compile-time (demo_policy.yaml / Vajra.md) and enforces rules at runtime via constant-time $\mathcal{O}(1)$ memory bitmaps with instant physical fusing (Strict Fail-Closed)!


Related MCP server: Proofpane

🌟 Hacker Edition Key Features (100% Free Forever for Individuals)

  • 🛡️ Protect Up to 5 Concurrent Agents: Simultaneously govern multiple active agents across different IDEs on a single host.

  • 🔑 Native W3C did:key & RFC-010 Passports: Cryptographic agent identity binding with Ed25519 signatures.

  • Microsecond In-Band Fusing (<1μs): Deterministic $\mathcal{O}(1)$ AST policy lookup that severs unauthorized syscalls before execution.

  • 📜 SHA-256 Merkle Hash-Linked Audit Chain: Non-repudiable local execution logs with startup recovery to prevent log tampering.

  • 🌐 Universal Cross-Ecosystem Compatibility: Native REST and MCP endpoints compatible with AGY, Claude, Codex, Cursor, LangChain, CrewAI, and DSH.


📊 Governance & Defense Capability Matrix

Threat Vector / Capability

Traditional LLM Guardrails

📦 DSH Standalone TS Plugin

⚡ DROS Hacker Docker Gateway (This Repo)

🏢 Enterprise / Mesh Tier

Runtime Vehicle

Cloud API / External Model

In-Process JS (Zero Deps)

Local Docker Container (:8080)

Enterprise Cluster / K8s / C-ABI

Protected Scope

Single Chat Session

DSH Local Process

Full Ecosystem (Claude+Codex+Cursor+DSH+AGY)

Multi-Node Fleet / Private Cloud

Destructive Command Blocking

❌ Vulnerable

🟢 100% Regex Failsafe

🟢 100% Deterministic AST Fusing (<1μs)

🟢 AST Bitmaps + eBPF Kernel Hooks

Credential & Secret Protection

❌ No Physical Guard

🟢 Sensitive Path Block

🟢 Dynamic PII Redaction + Virtual Sandboxing

🟢 Hardware HSM + ZKP-Lite Proofs

Agent Identity Binding

❌ No Identity

🟡 Session-level ID

🟢 Native W3C did:key (Ed25519)

🟢 3-Tier PKI DrosIdentityToken (DIT)

Non-Repudiable Audit Chain

❌ Plain Text Logs

🟢 Local SHA-256 Hash Chain

🟢 Ed25519 Signed Merkle Hash Chain

🟢 EU AI Act Art. 12 Court-Grade Chain

RFC-010 Passports

❌ Unsupported

🟡 Format Parser

🟢 Local Minting & Cross-Agent Verification

🟢 Cross-Organization Roaming Passports

Decision Latency

🔴 1,000 ~ 3,000 ms

🟢 <1 ms (Direct Hook)

🟢 <1 ms (Loopback HTTP / C-ABI)

🟢 <500 ns (Zero-Copy Memory Lookup)

License

Pay-per-Token

100% Free (Apache-2.0)

Free License for Individuals

Startup $2,990 / Enterprise $29,990


🛡️ Governance & Defense Capability Matrix

Threat Vector / Capability

Traditional LLM Guardrails (NeMo/Lakera)

📦 DSH Standalone TS Plugin

🛡️ DROS Hacker Docker Gateway

🏢 Enterprise / Mesh Tier

Runtime Vehicle

Cloud API / External Model

In-Process JS (Zero Deps)

Local Docker Container (:8080)

Enterprise Cluster / K8s / C-ABI

Protected Scope

Single Chat Session

DSH Local Process

Full Ecosystem (Claude+Codex+Cursor+DSH+AGY)

Multi-Node Fleet / Private Cloud

Execution Intent Governance

🔴 Text-matching only

🟢 Regex Pattern Failsafe

🟢 100% Deterministic AST Fusing (<1µs)

🟢 AST Bitmaps + eBPF Kernel Hooks

Destructive Command Blocking

🔴 Vulnerable to Injections

🟢 Sensitive Path Block

🟢 Deterministic Syscall Severing

🟢 Hardware HSM + Kernel-level Lock

Credential & Secret Protection

🔴 No Physical Guard

🟢 Sensitive Path Block

🟢 Dynamic Redaction + Sandbox Isolation

🟢 Hardware HSM + ZKP-Lite Proofs

Agent Identity Binding

🔴 No Identity

🟢 Session-level ID

🟢 Native W3C did:key (Ed25519)

🟢 3-Tier PKI DrosIdentityToken (DIT)

Non-Repudiable Audit Chain

🔴 Plain Text Logs

🟢 Local SHA-256 Hash Chain

🟢 Ed25519 Signed Merkle Hash Chain

🟢 EU AI Act Art. 12 Court-Grade Chain

RFC-010 Passports

🔴 Unsupported

🟢 Format Parser

🟢 Local Minting & Cross-Agent Verification

🟢 Cross-Organization Roaming Passports

Decision Latency

🔴 1,000 ~ 3,000 ms (Slow LLM)

🟢 <1 ms (Direct In-Memory Hook)

🟢 <1 µs (C-ABI) / <1 ms (REST Gateway)

🟢 <500 ns (Zero-Copy Memory Lookup)

License

Pay-per-Token API

100% Free (Apache-2.0)

Free License for Individuals

Startup $2,990 / Enterprise $29,990


🚀 Quick Start (One-Command Setup)

# Option A: One-Command Clone & Start (Self-Contained & Recommended)
git clone https://github.com/Top-Celestial-Company-Ltd/DROS-VajraClaw-Hacker.git
cd DROS-VajraClaw-Hacker
docker compose -f docker/docker-compose.yml up -d

# Option B: Run via GitHub Container Registry (GHCR)
docker run -d -p 8080:8080 --name dros-gateway \
  -v $(pwd)/demo_policy.yaml:/app/demo_policy.yaml:ro \
  ghcr.io/top-celestial-company-ltd/dros-vajraclaw-hacker:latest

# Verify Health Status
curl http://localhost:8080/health

Option 2: Build & Run from Source

git clone https://github.com/Top-Celestial-Company-Ltd/DROS-VajraClaw-Hacker.git
cd DROS-VajraClaw-Hacker
docker compose -f docker/docker-compose.yml up -d

🔌 5 Major Agent Ecosystem Integration Guides

See examples/ for working starter templates:

1. 🤖 Anthropic Claude Desktop & Claude Code (MCP Protocol)

See examples/claude_mcp/: Add to your claude_desktop_config.json or mcp_settings.json:

{
  "mcpServers": {
    "dros-vajraclaw": {
      "url": "http://localhost:8080/mcp",
      "transport": "http"
    }
  }
}

2. 💻 Cursor IDE / VS Code Agents (Terminal Protection)

See examples/cursor_rules/: Place .cursorrules in your project root to intercept high-risk terminal commands via http://localhost:8080/evaluate in <1μs before OS execution!

3. 🐍 OpenAI SDK & LangChain (3-Line Tool Wrapping)

See examples/openai_langchain/:

from integrations.vajraclaw.runtime import VajraClaw

vc = VajraClaw("demo_policy.yaml")
decision = vc.evaluate("execute_payment", {"amount": 500})
if not decision:
    raise PermissionError(f"Blocked by DROS: {decision.reason}")

4. 👥 CrewAI & Microsoft AutoGen (Multi-Agent Swarm Governance)

See examples/crewai_autogen/: Assign individual W3C DIDs to different agent roles (Legal, Dev, Auditor) and enforce fine-grained capability bitmaps across agent swarms.

5. 📦 DeepSeek Harness (DSH Dual-Mode Plugin)

See examples/dsh_plugin/:

dsh plugin --profile web add dsh-plugin-vajraclaw

(Set gatewayUrl to http://localhost:8080 in DSH to activate W3C DID & full Docker gateway governance)



📝 How to Configure Security Policies (Vajra.md Guide)

DROS supports two straightforward formats: Intuitive Markdown (Vajra.md) and Structured YAML (demo_policy.yaml).

1. 📄 Intuitive Markdown Example (Vajra.md)

Declare allowed capabilities and hard security boundaries in plain Markdown:

# 🛡️ DROS Agent Security Policy (Vajra.md)

## 1. Allowed Capabilities
- Allow reading workspace files (`file_read`)
- Allow standard queries (`search_web`, `query_db`)
- Allow safe terminal commands (`git status`, `npm test`, `cargo check`)

## 2. Strict Fail-Closed Boundaries
- Block all recursive deletion or wiping commands (`rm -rf`, `rmdir /s`, `format`)
- Block access to credential paths (`.env`, `id_rsa`, `secrets.json`, `.aws/credentials`)
- Restrict transaction amounts exceeding $1,000 threshold (`amount <= 1000`)

IMPORTANT

🔒Crucial Security Best Practice: Lock Vajra.md to Read-Only After Configuration! To prevent compromised or hallucinating AI Agents from attempting to rewrite their own security rules to escalate privileges, always set your policy file to read-only once configured:

  • Linux / macOS: chmod 444 Vajra.md

  • Windows (PowerShell): Set-ItemProperty -Path Vajra.md -Name IsReadOnly -Value $true

  • Docker Container Mount: Mount with the read-only flag -v $(pwd)/Vajra.md:/app/demo_policy.yaml:ro

(Note: DROS kernel enforces 4-Layer Invariant Defense to intercept unauthorized policy modifications in-band; combining this with OS file-level locks achieves 100% airtight physical defense!)

2. 🤖 Let AI Generate Your Policy in 1 Second! (AI Prompt Template)

You don't need to write policies from scratch! Copy the following universal prompt to ChatGPT, Claude, or Cursor:

📋 Copy this Prompt to any LLM / AI Assistant:

You are a DROS deterministic security architecture expert. Based on my Agent requirements, generate a standard DROS "Vajra.md" security policy in Markdown.

Agent Details:
- Agent Role & Scenario: [e.g., Fullstack Developer / Customer Service / Financial Automation]
- Allowed Tools & Operations: [e.g., Read/Write src/, Run tests, Query order database]
- Strict Boundaries & Denials: [e.g., Block deletion of root/workspace, Block .env access, Payment limit $500]

Follow the DROS "Default Fail-Closed" whitelist principle and structure the output into:
1. Role & Capability Scope
2. Allowed Capabilities (Whitelist)
3. Security Boundary Constraints (Thresholds & Pattern Failsafes)

3. 🔄 Instant Hot Reloading

Simply mount your Vajra.md when launching the Docker gateway. Policy changes take effect in <1 microsecond without container restarts:

docker run -d -p 8080:8080 --name dros-gateway \
  -v $(pwd)/Vajra.md:/app/demo_policy.yaml \
  dros/hacker-gateway:v1.0.0

📜 Technical Foundations & Benchmark Publications

The deterministic execution governance, microsecond fusing, and cryptographic audit mechanisms in this project are referenced from and build upon the following core technical papers and verification environments:

  1. Core Architecture & Six Trust Boundaries (Core Architecture):

  2. Defense-in-Depth Model (4-Layer Security):

  3. Runtime Attribution & C-ABI Module (Attribution Framework):

  4. Open Standards & Verification Sandbox:

    • RFC-010 Specification: Adheres to open Agent Identity & Attestation standard (W3C DID did:key & Ed25519 signature chain).

    • Verification Sandbox: DROS-VEP Lite (Reproducible Evaluation Sandbox)

    • Evaluation Metrics: 24-hour soak benchmark results (160,611 verified requests, 26.1μs decision latency).


⚠️ Important Notices & Operational Security

  1. Strict Fail-Closed Enforcement:

    • By default, any capability or syscall not explicitly declared as ALLOW in demo_policy.yaml is permanently blocked.

  2. Privilege Separation:

    • The AI Agent must never possess write permissions to policy files. In production, mount policy files as Read-Only.

  3. License Key Activation (Optional):

    • Out-of-the-box, the gateway runs in Community mode (supporting 2 concurrent agents). To unlock 5 concurrent agents, pass -e DROS_LICENSE_KEY="your-key" or activate via DSH settings.


⚖️ Standard 3-Tier License & Intellectual Property Constitution

  • Personal & Community Use (Free for Individuals):

    • Granted permanently for individual developers and researchers (Free License for Individuals) on up to 1 host and 5 concurrent agents. Source code and patent claims are proprietary. Unauthorized redistribution or reverse engineering is strictly prohibited.

  • Enterprise & Commercial Deployment:

    • Enterprise implementation or use by corporate entities requires commercial licensing (Startup / Enterprise / Sovereign). Contact service@dr-os.io or visit https://dr-os.io.

  • Patent Notice:

    • DROS deterministic runtime governance and in-band interception technology is protected under U.S. Provisional Patent Application (U.S. PPA No. 64/111,973, Patent Pending). All commercial and enterprise rights are reserved by Top-Celestial Company Ltd.

Available Tools

1 tool
dros_evaluateC

Deterministic in-band execution guardrail evaluating actions in sub-microsecond latency.

ParametersJSON Schema
NameRequiredDescriptionDefault
capabilityYes
parametersNo

TDQS

C2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'deterministic' and 'sub-microsecond latency', which are useful behavioral traits, but it does not explain side effects, whether the tool blocks/allows execution, return values, or failure modes. The key behavior—what happens with the evaluation result—is left unspecified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no redundancy—it is concise in the sense of being short. However, it under-specifies the tool so severely that the brevity is more a symptom of incompleteness than effective conciseness. It is not bloated, but it doesn't earn its place as a useful summary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema and no annotations, the description must carry a heavy burden. It gives only a vague functional hint and a couple of non-functional attributes, but fails to describe inputs, outputs, side effects, or evaluation semantics. The tool is not adequately contextualized for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain or even mention the parameters 'capability' or 'parameters'. There is no indication of what values 'capability' accepts or what structure 'parameters' should follow. The description adds no meaning beyond the bare schema, leaving the agent unable to construct a valid invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses vague, jargon-heavy language ('in-band execution guardrail', 'evaluating actions') without clarifying concretely what the tool does. The verb 'evaluating' and resource 'actions' are generic, and the purpose remains ambiguous—it is not obvious what action is evaluated, how, or for what decision.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given about when to use this tool. With no sibling tools listed, there are no alternatives to contrast against, but the description also lacks any context about the intended invocation scenario or prerequisites. The agent is left to infer usage entirely from the tool name and vague description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

TDQS

C2.9/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion between tools. The purpose is clearly defined as a deterministic execution guardrail.

Naming Consistency5/5

The single tool name 'dros_evaluate' uses a clear verb_noun style. With only one tool, naming consistency is trivially satisfied.

Tool Count5/5

The server has a narrowly scoped purpose, acting as a single guardrail evaluation function. One tool fully serves that purpose without unnecessary extras.

Completeness5/5

For its stated domain of evaluating actions as a guardrail, the single tool covers the necessary functionality completely. There are no obvious missing operations within this narrow scope.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    A secure MCP gateway for enterprise AI tool execution, enabling governed invocation of business tools with authentication, RBAC, audit logging, PII redaction, and async processing.
    Apache 2.0
  • A
    license
    B
    quality
    A
    maintenance
    A governance proxy for AI tools — every MCP/agent tool call is policy-gated, secret-redacted, and written to a hash-chained, offline-verifiable audit trail.
    13
    MIT
  • A
    license
    B
    quality
    C
    maintenance
    MCP zero-trust gateway that sits in front of every internal MCP server, detects tool-poisoning/metadata drift in real time, and maintains a cryptographic provenance ledger of every agent tool call.
    20
    2
    ISC
  • A
    license
    Not graded
    quality
    B
    maintenance
    Self-hosted MCP gateway that applies deterministic, compiled policy to tool discovery, invocation, and outbound data flow, with no model in the enforcement path. Every decision emits a hash-chained receipt sealed with Ed25519 and verifiable using public keys only.
    Apache 2.0

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Top-Celestial-Company-Ltd/DROS-VajraClaw-Hacker'

If you have feedback or need assistance with the MCP directory API, please join our Discord server