Skip to content

Propagation breaker for agent fleets

by textforagents.com · remote · no sign-in to list tools · v1.0.0 · published by com.textforagents

Propagation breaker: egress quarantine + fingerprint outbreak telemetry for fleets.

Changes · 5
CompareRegistry entry

6 tools: 5 change things and 1 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http propagation-breaker-agent-worms https://textforagents.com/products/propagation-breaker-agent-worms/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

6 tools

Changes things 5Claude Code: ask
  • controls_verifyVerify loop-breaking controls are on and untampered.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
    Verify loop-breaking controls are on and untampered.
  • egress_checkScore an outbound message against inbound context; quarantine worm forwards.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
    Score an outbound message against inbound context; quarantine worm forwards.
  • store_readRead from the shared store; data context unless a valid elevation token is given.No findings

    Why it is in this group

    • The name "store_read" says "store": a word for a change.
    Description, as the server wrote it
    Read from the shared store; data context unless a valid elevation token is given.
  • store_writeWrite to the shared store (data-only by default).No findings

    Why it is in this group

    • The name "store_write" says "store": a word for a change.
    Description, as the server wrote it
    Write to the shared store (data-only by default).
  • telemetry_reportPer-cluster spread telemetry and R estimates.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
    Per-cluster spread telemetry and R estimates.
Only reads 1Claude Code: allow
  • fingerprint_queryHas this payload fingerprint been seen propagating in the fleet?No findings

    Why it is in this group

    • The name "fingerprint_query" says "query": a word for reading.
    Description, as the server wrote it
    Has this payload fingerprint been seen propagating in the fleet?

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.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http propagation-breaker-agent-worms https://textforagents.com/products/propagation-breaker-agent-worms/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__propagation-breaker-agent-worms__fingerprint_query"
    ],
    "ask": [
      "mcp__propagation-breaker-agent-worms__egress_check",
      "mcp__propagation-breaker-agent-worms__store_write",
      "mcp__propagation-breaker-agent-worms__store_read",
      "mcp__propagation-breaker-agent-worms__telemetry_report",
      "mcp__propagation-breaker-agent-worms__controls_verify"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as propagation-breaker-agent-worms. Review it before you use it.