MCP Security Engineering · Active L2 Track

MCP Security Engineering L2 Track

Intermediate learning path for designing and reviewing Model Context Protocol security boundaries without running live MCP clients, servers, tools, credentials, or production integrations.

StatusActive Track

Modules2 of 9

DomainAI Security

RuntimeRead-only course

Overview

This track teaches MCP security engineering from a static, reviewer-safe perspective: server trust, client authority, tool permission scope, context injection, data exposure, approval gates, evidence capture, and control mapping.

MCP is treated as a security design surface, not as a live integration target. Learners reason about boundaries and controls without running MCP servers, connecting tools, handling credentials, or mutating systems.

Planned Module Map

1. MCP Security Engineering Overview Introduce MCP trust boundaries, tool authority, context flow, approval requirements, evidence capture, and non-execution constraints. 2. MCP Server Trust Boundary Design Implemented LAB - production quality-gated. Plan how MCP server identity, trust, ownership, and allowed resources should be reviewed.

3. MCP Tool Authority and Permission Scope Reason about tool permission boundaries, least privilege, sensitive actions, and execution authority.

4. MCP Context Injection Risk Design Design safe scenarios for reviewing untrusted context, source authority, prompt boundaries, and instruction hierarchy.

5. MCP Data Exposure Scenario Design Review sensitive data boundaries, resource access, tenant separation, and disclosure controls using synthetic examples.

6. MCP Approval Gate and Human-in-the-Loop Controls Evaluate where human approval, escalation, and recommendation-versus-execution separation must remain intact.

7. MCP Agent Workflow and Tool Abuse Review Review agentic MCP workflows for tool abuse, loop risk, over-permissioning, and unsafe automation assumptions.

8. MCP Evidence Capture and Control Mapping Capture reviewer-safe evidence and map observations to controls without collecting secrets or runtime artifacts.

9. MCP Security Engineering Capstone Combine MCP boundary review, evidence capture, risk explanation, control mapping, and executive-ready reporting.

Governance Boundary

This is a static educational track. It does not run MCP servers, start MCP clients, invoke tools, handle credentials, connect to production systems, or claim production enforcement.

Track implemented = true
LAB modules implemented = 2 of 9
Backend exposure = false
Public backend exposed = false
MCP server execution = false
MCP client execution = false
Live tool invocation = false
Credential handling = false
Customer data access = false
Runtime mutation = false
Production enforcement claim = false