Propagation breaker: egress quarantine + fingerprint outbreak telemetry for fleets.
Scored across 6 tools
Each tool targets a clearly distinct function: control verification, outbound message scoring, fingerprint lookup, store read, store write, and telemetry reporting. The read/write pair is explicitly differentiated by direction and the remaining tools do not overlap.
All six tools follow a uniform noun_verb convention (controls_verify, egress_check, fingerprint_query, store_read, store_write, telemetry_report). The pattern is applied consistently across the whole surface with no style mixing.
Six tools is a well-scoped set for a focused propagation-breaking server, covering detection, control integrity, storage, and telemetry without bloat. Each tool earns its place.
Core detection, verification, and telemetry operations are covered, but quarantine management (listing/releasing quarantined items) and explicit fingerprint ingestion are missing. These are minor gaps that the store and egress tools may partially work around.
Verify loop-breaking controls are on and untampered.
Score an outbound message against inbound context; quarantine worm forwards.
Has this payload fingerprint been seen propagating in the fleet?
Read from the shared store; data context unless a valid elevation token is given.
Write to the shared store (data-only by default).
Per-cluster spread telemetry and R estimates.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Partition an agent fleet into reputation compartments with automatic firebreaks.
Good-neighbor traffic passport: signed per-host budgets, egress governor, compliance receipts
Salvageability triage for agent fleets in a declared mass-failure mode.
Agent-speed defense for your own public surfaces: daily diff probes, per-identity verdicts.
Add one secure layer between your agents and this server.
