Skip to content
Roadmap0/111
not startedstudy day 6 of 6 · covers original day 38

Study MCP architecture

P3 Agent systemS3D2
not started0/5 blocks
0/5
Jump & context

Week 5: RAG ACLs, PII UUID Gateway, Training-Data Poisoning & Agent/MCP Foundations

The five hours

  1. 01

    Concepts & system design

    60 min

    R21 — MCP Specification: architecture, lifecycle, transports, and security

    Read the assigned sections; map the mechanism, threat model and trade-offs.

  2. 02

    Project implementation

    120 min

    Study Model Context Protocol (MCP) architecture: client/server roles, tool discovery, JSON-RPC 2.0 messages, transports, and trust boundaries. Build a local MCP server exposing 2 safe repository-exploration tools.

    Build, integrate, debug and improve the increment in the active project.

  3. 03

    Security lab

    60 min

    Map every trust boundary between the LLM, agent host, MCP client, mcp-proxy (D2), and MCP server.

    Test the abuse case, failure path, authorization bypass or resource limit.

  4. 04

    Verification & evidence

    30 min

    Working local MCP server + protocol data-flow and trust-boundary diagram.

    Add or run regression tests; record the 9-point evidence record.

  5. 05

    Deliberate practice & Socratic review

    30 min

    Answer the 8 Socratic questions without notes: What? Why? How? What if? Why not? How can I prove it? Where can it break? What have I learned?

    Re-explain the hardest concept aloud, inspect one edge case, update the gap log.

  6. total5 h

Read today · inside the concepts block

R21

Read only the named sections needed for today's task. Reading sits inside the 60-minute concepts block; it is not extra time.

Free resources for this day

5 curated

Evidence record · 9-point standard

0/9

A lab is complete only when it produces evidence. Installing PyRIT, Garak, Presidio or TransformerLens is not completion. Saved on this device only.

Day notes

empty

The two source formulations

verbatim · nothing summarised

Project & Deliverable Target

P3 | `D2` (Sandboxed MCP Proxy) | S3

Core Implementation

Study Model Context Protocol (MCP) architecture: client/server roles, tool discovery, JSON-RPC 2.0 messages, transports, and trust boundaries. Build a local MCP server exposing 2 safe repository-exploration tools.

Security Lab

Map every trust boundary between the LLM, agent host, MCP client, mcp-proxy (D2), and MCP server.

Verification & Evidence

Working local MCP server + protocol data-flow and trust-boundary diagram.

Read Today (60m Concepts Block)

R21 (MCP Specification: architecture, lifecycle, transports, and security).

---