Ban Bulkheads — Reputation Firebreaks for Agent Fleets MCP server
com.textforagents/ban-bulkheads-reputation-firebreakstextforagents.comstreamable-httpv1.0.0Scanned
Partition an agent fleet into reputation compartments with automatic firebreaks.
9 tools: 8 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
8 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Ban Bulkheads — Reputation Firebreaks for Agent Fleets MCP server can do
The Ban Bulkheads — Reputation Firebreaks for Agent Fleets MCP server is published by textforagents.com, a domain the MCP Registry verified. It has 9 tools. It can create or change data (8 tools: create_compartment, assign_agent, record_outcome, add_job and 4 more), but cannot delete data. 1 tool only reads.
1 tool brings in text other people can write (status_query).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 3, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
9 tools
Changes things 8Claude Code: ask
add_jobRegister an in-flight job {compartment, job_id, clean}No findings
Why it is in this group
- The name "add_job" says "add": a word for a change.
Description, as the server wrote it Register an in-flight job {compartment, job_id, clean}
assign_agentAssign an agent to a compartment {agent, compartment}No findings
Why it is in this group
- The name "assign_agent" says "assign": a word for a change.
Description, as the server wrote it Assign an agent to a compartment {agent, compartment}
create_compartmentCreate a reputation compartment {task_class} (plan slot required)No findings
Why it is in this group
- The name "create_compartment" says "create": a word for a change.
Description, as the server wrote it Create a reputation compartment {task_class} (plan slot required)
freeze_compartmentFreeze a compartment {compartment}No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Freeze a compartment {compartment}
penalty_signalIntake an account-level penalty signal {kind}; attribution comes from baselines onlyNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Intake an account-level penalty signal {kind}; attribution comes from baselines only
readmitRe-admission probes {compartment, probes}No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Re-admission probes {compartment, probes}
receiptsIncident receipt chain + validityNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Incident receipt chain + validity
record_outcomeRecord an outcome {compartment, outcome, job_id?, job_clean?}No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Record an outcome {compartment, outcome, job_id?, job_clean?}
Only reads 1Show 1 read-only tool
status_queryCompartment status for an agent {agent} — $0.01 x402 or included on an active plan (same billing as HTTP)Reads text others writeNo findings
Why it is in this group
- The name "status_query" says "status": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "http": it reads web pages, which anyone can write.
Description, as the server wrote it Compartment status for an agent {agent} — $0.01 x402 or included on an active plan (same billing as HTTP)
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:26 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 8
- Protocol version
- 2024-11-05
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 8 tools that change things (8 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://textforagents.com/products/ban-bulkheads-reputation-firebreaks/mcp: tools/list returned 9 tools to an anonymous client, including create_compartment (write), assign_agent (write), record_outcome (write), add_job (write), penalty_signal (write) and 3 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http ban-bulkheads-reputation-firebreaks https://textforagents.com/products/ban-bulkheads-reputation-firebreaks/mcpclaude mcp add --transport http ban-bulkheads-reputation-firebreaks https://textforagents.com/products/ban-bulkheads-reputation-firebreaks/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__ban-bulkheads-reputation-firebreaks__status_query"
],
"ask": [
"mcp__ban-bulkheads-reputation-firebreaks__create_compartment",
"mcp__ban-bulkheads-reputation-firebreaks__assign_agent",
"mcp__ban-bulkheads-reputation-firebreaks__record_outcome",
"mcp__ban-bulkheads-reputation-firebreaks__add_job",
"mcp__ban-bulkheads-reputation-firebreaks__penalty_signal",
"mcp__ban-bulkheads-reputation-firebreaks__freeze_compartment",
"mcp__ban-bulkheads-reputation-firebreaks__readmit",
"mcp__ban-bulkheads-reputation-firebreaks__receipts"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ban-bulkheads-reputation-firebreaks. Review it before you use it.
Capability tags behind 1 rule
- mcp__ban-bulkheads-reputation-firebreaks__status_query untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.textforagents/ban-bulkheads-reputation-firebreaks/verify?hash=930b1ca2c73f95a22d4f2f1dc507a5fbe676a45c10caa10d558f3fdbf97deacc" | jq -e '.changed == false'Pinned hash 930b1ca2c73f, from Nov 3, 2026, 19:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.textforagents/ban-bulkheads-reputation-firebreaks/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.textforagents/ban-bulkheads-reputation-firebreaks)Source: MCP Registry. Synced Oct 21, 2026, 18:06 UTC.
Ban Bulkheads — Reputation Firebreaks for Agent Fleets MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Ban Bulkheads — Reputation Firebreaks for Agent Fleets MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, 8 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Ban Bulkheads — Reputation Firebreaks for Agent Fleets MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Ban Bulkheads — Reputation Firebreaks for Agent Fleets MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Ban Bulkheads — Reputation Firebreaks for Agent Fleets MCP server have?
- 9 tools: 8 write, 1 read. create_compartment, assign_agent, record_outcome, add_job, penalty_signal, freeze_compartment, readmit, receipts and 1 more.
Does the Ban Bulkheads — Reputation Firebreaks for Agent Fleets MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Ban Bulkheads — Reputation Firebreaks for Agent Fleets MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Ban Bulkheads — Reputation Firebreaks for Agent Fleets MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 3, 2026.