AGENTIC AI 75 · #33
Pathology agents as interoperable MCP tools
Owkin announced MCP-compatible biological agents, including tools for digital pathology analysis.
Last reviewed 2026-11-11
Agentic AI 75 / #33
2026 status: Product and infrastructure announcement · Category: Clinical tools
The 2026 development
Owkin announced MCP-compatible biological agents, including tools for digital pathology analysis.
The governance gap
MCP makes a specialist capability callable by any agent. A callable pathology tool needs input validation, PHI boundaries, a named responsible clinician and a refusal path for out-of-scope images.
Where CAIN-42 fits: Moat 2 — Security-Context Continuity
Core question: Does authority survive every boundary? Identity, scope and delegation are carried across tools, agents, memories and systems.
Treat the tool definition as part of the security surface. CAIN's MCP scanner grades the definition; the proxy validates arguments and tenant scope; the decision record names the tool version and caller.
How the wiring works
- Scan the tool definition for description injection and unsafe schemas.
- Validate image references and patient identifiers before the call.
- Enforce a tenant and purpose boundary on the request.
- Record the tool version, caller and result digest.
What is real today
LIVE A public route in this deployment exercises this mechanism today, within its stated scope.
The scanner and proxy are real. This is not a clinical device, not Owkin, and not autonomous diagnosis.
| Component in this repository | What the module says it is |
|---|---|
cain/mcp_proxy.py | CAIN Trust Fabric - Universal MCP Transparent Interceptor & Proxy (Phase 2) |
mcp-security-scanner/engine.py | Real MCP tool-schema security scanner. |
cain/tool_metadata_guard.py | MCP tool-metadata guard: tool poisoning and rug-pull defence for `tools/list`. |
Descriptions are the first line of each module's own docstring, read without importing it. A module path is a pointer into this repository, not a hosted endpoint. Its existence is checked by the test suite; its status for this use is the label above.
Check it yourself
- Scan a live MCP tool definition
/mcpgate-keystone - Fire a live decision through the CAIN-42 pipeline
/fabric/try— the same enforcement path every product sits behind.
Commercial package
| Offer | Clinical Tool Boundary Review |
|---|---|
| Buyer | Clinical AI vendors and hospital IT |
| Price (proposal) | $5,000–$12,000 per review |
| Bundle | Identity & Authority — Every agent, every delegation, every boundary. |
| Operator stream | Stream 2 of the 10-stream operator playbook |
CISO, IAM, platform security, agent-tool vendors is the bundle buyer. The entry offer for this bundle is Agent authority review; MCP/A2A boundary review; the range is $2,500–$7,500 per review; integration from $10,000. A price on this page is a proposal, not a validated rate, and no customer is claimed.
Buy this as a product or service
CAIN-A75-033 — Clinical Tool Boundary Review DELIVERABLE
A bounded engine run on the buyer's sample: findings, a written report, and a SHA-256 artifact manifest. The manifest is unsigned: it is not a signature and not an attestation.
Kind: Assessment · Price (proposal): $5,000–$12,000 per review · Lead time: 5 business days.
Open the product page · all 75 products
What this page does not claim
What this page is not. CAIN-42 is not affiliated with, endorsed by, integrated into, or shipped with the organisation named in the 2026 item. The item is public context; the page describes how CAIN-42 would govern that class of capability. No page here claims a customer, a partnership, a certification, a patent, or a production integration. Prices are proposals. Built by a three-person team.