Generative AI
ExperimentalMCP (live red-team)
Attacks a live MCP server: enumerates its tools and maps description-poisoning, schema-drift and rug-pull to the MCP invariants, promoted by the membrane.
Family facts
- Code
- FAM-GENAI-MCP-LIVE
- Status
- experimental — code maturity
- Availability
- experimental — whether it is offerable
- Ingest
- live — how a target enters
- Rules of Engagement
- Required (acts on a live target)
- Kind
- Family (a selectable assessment)
What it decides
Whether a running MCP server exhibits a tool-poisoning, drift or rug-pull condition — proven against the live server.
How it works
The live-scan mission enumerates a running server’s tools over the protocol and maps what it finds to the same MCP invariants as the static family, crossing the membrane for promotion.
It is experimental because today it is reachable only directly with an operator-supplied scanner configuration; live ingest delivers only a bare endpoint, so promoting it needs a connector-config builder and a live→config adapter.
Declared limits
Experimental and not runnable from the platform: reachable only directly, and not yet wired into the platform’s run flow.
References
References point to public, well-known technical sources for further study.
Related articles