BLACK_WALL

BLACKWALL gives your agent a brake.

CommunityOnlineAPI key requiredGlobalFreeCan modify data

What it can do

  • Forecast: Call this BEFORE taking ANY irreversible or high-stakes action — sending an email, making a payment, running SQL, deleting files or data, posting public content, or calling an external API t

What data it sees

Do you need an account

An API key from the service settings is required

BLACK_WALL gives your agent a brake. It exposes a single tool, forecast, that the agent calls before any irreversible action — sending an email, making a payment, running SQL, deleting data, posting content.

It returns:

  • a risk score (0–100)
  • a reversibility class + rollback cost (reversible / recoverable / irreversible)
  • a gate: proceed / confirm / human-required
  • named red flags from 28 documented failure modes (SQL_NO_WHERE, INTENT_MISMATCH, CROSS_ENVIRONMENT, MASS_RECIPIENT, PROMPT_INJECTION_LIKELY, …)

A normal email clears in one call; a DROP TABLE on prod comes back STOP / human-required — before it runs. The agent can't talk itself into the bad action, because the verdict is a hard gate.

Setup: paste your BLACK_WALL API key as the apiKey parameter. Get one free at https://blackwalltier.com (~100 forecasts/month, no card). A verdict takes ~4–8s.

A BLUETIER product.

How to connect

How to connect BLACK_WALL to Claude

The server address to paste into Claude settings:

https://blackwall--bluetier-operations.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect BLACK_WALL to ChatGPT

The server address to paste into ChatGPT settings:

https://blackwall--bluetier-operations.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect BLACK_WALL to Cursor

The server address to paste into Cursor settings:

https://blackwall--bluetier-operations.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (1)

Raw names from tools/list. Only developers need these.

forecastCall this BEFORE taking ANY irreversible or high-stakes action — sending an email, making a payment, running SQL, deleting files or data, posting public content, or calling an external API that changes state. Returns a risk score (0–100), a recommendation (GO / CAUTION / STOP), and named red flags. If STOP, do not act — surface the flags to the user. If CAUTION, confirm with the user first.