BLACK_WALL — Pre-action risk gate for AI agents

by bluetieroperations-create

279 downloads
Not rated
GitHub

About

A single `forecast` tool your agent calls before any irreversible action (send money, run SQL, delete data, post content). Returns a risk score (0–100), a reversibility class, named red flags from 28 failure modes, and a gate: proceed / confirm / human-required.

Details

Author
bluetieroperations-create
Downloads
279
Categories
Developer Tools, Security, AI, Other

- Single forecast tool for pre-action risk assessment
- Risk score from 0–100 and reversibility class with rollback cost
- Gate verdict of proceed, confirm, or human-required
- 28 documented failure modes with named red flags (e.g. SQL_NO_WHERE, PROMPT_INJECTION_LIKELY)
- Hard gate that the agent cannot override
- Verdict in approximately 4–8 seconds

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

  1. Download and install Highlight from highlightai.com/download
  2. Navigate to the plugins tab and select "Add Custom Plugin"
  3. Configure the plugin with the settings below
    Plugin Name BLACK_WALL — Pre-action risk gate for AI agents
    Command (node, npx, python, etc.)

    Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.

  4. Enable "Start Automatically" if you want the plugin to start when Highlight launches

From the repository

Configure BLACK_WALL in your MCP-compatible client (Claude Desktop, Claude Code, Cursor, or Windsurf) by adding a JSON block with the npx command and your API key. The agent then invokes the forecast tool before each potentially irreversible action; a normal email clears in one call, while a dangerous action returns a hard gate verdict.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "black_wall \u2014 pre-action risk gate for ai agents": {
            "blackwall": {
                "command": "npx",
                "args": [
                    "-y",
                    "blackwall-mcp"
                ],
                "env": {
                    "BLACKWALL_API_KEY": "bw_live_your_key_here"
                }
            }
        }
    }
}

McpServers

{
    "blackwall": {
        "command": "npx",
        "args": [
            "-y",
            "blackwall-mcp"
        ],
        "env": {
            "BLACKWALL_API_KEY": "bw_live_your_key_here"
        }
    }
}

A guardrail for AI agents, as an MCP server.Your agent calls one tool —forecast— before any irreversible action (send email, move money, run SQL, delete data, post content). It gets back a risk score (0–100), a reversibility class, aGO/CAUTION/STOPrecommendation, and named red flags in a few seconds (~4-8s).

Works in any MCP host:Claude Desktop, Claude Code, Cursor, Windsurf, and any agent framework with MCP support.

The wall between your agent and disaster. A BLUETIER product.

Sign up free athttps://blackwalltier.com→ Dashboard → API keys → Create key. Free tier: ~100 forecasts/month, no card. Your key looks likebw_live_….

Editclaude_desktop_config.json(Settings → Developer → Edit Config):

{ "mcpServers": { "blackwall": { "command": "npx", "args": ["-y", "blackwall-mcp"], "env": { "BLACKWALL_API_KEY": "bw_live_your_key_here" } } } }

Restart Claude Desktop. You'll see aforecasttool available.

Settings → MCP → Add new global MCP server, then inmcp.json:

{ "mcpServers": { "blackwall": { "command": "npx", "args": ["-y", "blackwall-mcp"], "env": { "BLACKWALL_API_KEY": "bw_live_your_key_here" } } } }
claude mcp add blackwall -e BLACKWALL_API_KEY=bw_live_your_key_here -- npx -y blackwall-mcp
BLACKWALL_API_KEY=bw_live_your_key_here npx -y blackwall-mcp

Once added, instruct your agent:"Before any irreversible action, call theforecasttool and stop if it returns STOP."The model will call it automatically when it's about to do something risky.

Returns:recommendation (GO/CAUTION/STOP),risk_score(0–100),reversibility(class + rollback cost),gate(proceed/confirm/human-required),confidence,red_flags[],predicted_result,alternative_actions[].

Agent about to runDELETE FROM users;(no WHERE clause) →

🛑 BLACK_WALL: STOP — risk 99/100 Red flags: • [CRITICAL] SQL_NO_WHERE — deletes the entire table, not one row • [CRITICAL] INTENT_MISMATCH — intent was "remove a single test row" • [CRITICAL] IRREVERSIBLE_NO_BACKUP — no recovery path Guidance: DO NOT take this action. Surface the red flags to the user.

Not ready to let a guardrail block your agents? Start inobserve mode. It scores and logs every action butnever tells the agent to stop— your agents behave exactly as they do today. After a week, review your dashboard and see what itwouldhave caught.

{ "mcpServers": { "blackwall": { "command": "npx", "args": ["-y", "blackwall-mcp"], "env": { "BLACKWALL_API_KEY": "bw_live_your_key_here", "BLACKWALL_MODE": "observe" } } } }

Then see"what your agents almost did"in your dashboard. FlipBLACKWALL_MODEtoenforce(or just remove it — enforce is the default) when you're ready to actually block.

- forecast— pre-action risk check. ReturnsGO/CAUTION/STOP, risk score, named red flags, reversibility class, and a verifiable receipt.
- observe— post-action outcome report. Tells BLACK_WALL what actually happened after the action ran (or after the agent obeyed a STOP verdict). Closes the loop so the system can track prediction accuracy over time. FREE — no tokens charged.

Wire your agent to callforecastbefore any irreversible action, then callobserveafterwards with theforecast_idfrom the original response.observeaccepts anoutcome_class(matched/over_scope/under_scope/no_op/diverged/aborted) and optionaldivergence_severityanddetails. See theforecastexample below; the same wiring applies toobserve.

Use it in code — thegate()control (any JS/TS agent)

Running an agent in Node (LangChain, a custom loop, ElizaOS, a cron job)? You don't need an MCP host — call BLACK_WALL straight from the library, and letgate()make the checkimpossible to skip. One wrap forecasts the action, enforces the verdict (fails closedonSTOP/ unknown / unreachable), runs your side effect only when allowed, and reports the real outcome withobserveautomatically.

import { gate, BlackWallBlocked } from 'blackwall-mcp/lib/gate'; // Wrap ANY risky action in a few lines. BLACKWALL_API_KEY lives in the env. try { const { result } = await gate( { action: 'run_sql', inputs: { statement: sql }, context: { user_intent } }, () => db.query(sql), // your real side effect — only runs if allowed { onCaution: (v) => confirmWithHuman(v) }, // CAUTION needs a yes; default = block ); // ...use result } catch (e) { if (e instanceof BlackWallBlocked) { // STOP, unconfirmed CAUTION, or forecast unavailable → the action NEVER ran console.error('Blocked:', e.reason, e.verdict?.red_flags); } else throw e; // a real error thrown by your action }

Fails closed by design.If no verdict can be obtained (network / auth / timeout), the action doesnotrun unless you explicitly passfailOpen: true. A risk gate that fails open is not a risk gate. The loop closes itself —gate()callsobservewith the actual outcome (matched/diverged/aborted), so your forecasts sharpen over time.

Prefer the lower-level pieces? They're exported too:

import { forecast, observe } from 'blackwall-mcp/lib'; const v = await forecast({ action: 'make_payment', inputs: { amount_usd: 50000 } }); if (v.recommendation === 'STOP') throw new Error('halt'); // ... take the action ... await observe(v.id, { outcome_class: 'matched' });

Runnable demo:examples/gate-quickstart.mjs.

Decision receipts (cryptographic, verifiable offline)

Everyforecastresponse now includes areceiptfield — an Ed25519 signature over canonical SHA-256 hashes of the request + response. Anyone with the published public key can verify offline that BLACK_WALL signed off on a specific (request, response) pair, without trusting our servers.

- Published keys:https://blackwalltier.com/.well-known/blackwall-signing-keys.json(stable, cacheable)
- Stateless verify endpoint:POST https://blackwalltier.com/api/v1/receipts/verifywith{ envelope, request_body, response_body }
- Hashes only — BLACK_WALL never stores the raw request/response bodies, so receipts give cryptographic audit without payload exposure
- Free-tier retention: 90 days. Paid: indefinite.

The MCP server surfaces the receipt id in its tool output so your agent can log it for later replay / audit.

- Site & docs:https://blackwalltier.com
- Get a key:
https://blackwalltier.com/dashboard/keys

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

Require a named human's offline-verifiable approval before an AI agent takes an irreversible action — payment release, record change, deploy. Two-person rule, Ed25519 Trust Receipts, IETF-drafted, Apache-2.0.

Six-gate governance for AI agents: PROCEED/PAUSE/HALT decisions with hash-chained audit trails.

EU AI Act compliance scanner for Python AI agents — 10 tools for scanning, analysis, and remediation

EXIF for AI. AKF embeds trust scores, source provenance, and compliance metadata into every file your AI touches — DOCX, PDF, images, code, and 20+ formats. 9 MCP tools: stamp, inspect, trust, audit, scan, embed, extract, detect. Audit against EU AI Act, SOX, HIPAA, NIST in one command.

Pre-connect trust checks for AI agents, frameworks, packages, and MCP servers using HVTracker's public trust registry.

Security scanner for MCP servers — detects tool poisoning, prompt injection, and 90+ vulnerability patterns

MCP server for security-vetting third-party AI agent extensions before installation — Claude skills, ClawHub plugins, agent tool packs. 41 detection rules; outputs 0-100 risk score + BLOCK/REVIEW/CAUTION/CLEAN.

Paid remote MCP for AI agent safety replay checks, policy gates, eval receipts, control-fix suggestions, and release evidence exports.

Cryptographic action receipts for AI agents. Signs every MCP tool call with Ed25519, hash-chained audit log. 3 lines of code to integrate.

Trust and safety layer for AI agents — scores MCP servers for security risk, capability flags, and prompt injection.

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.