What problem does it solve?
AI agents and IDEs that load Model Context Protocol (MCP) servers inherit serious trust risks: malicious tool descriptions can inject instructions into the model, local stdio servers can read user credentials, and config trust bypasses can yield RCE. This Skill provides a structured methodology to find and prove these issues during authorized penetration tests.
Core Features & Use Cases
- Tool Poisoning & Injection Testing: Build test MCP servers with the Python
mcp SDK to hide instructions in tool descriptions, parameter names, and outputs, then confirm execution via OOB callbacks.
- Credential Exposure & Config Trust Assessment: Model what a hostile stdio server could read (SSH keys, AWS/cloud credentials) and test MCPoison-style config swap bypasses (CVE-2025-54136) with benign marker payloads.
- Host RCE & Fuzzing: Test Flowise CustomMCP unauthenticated RCE (CVE-2025-59528, CVE-2025-8943) and fuzz SSE/WebSocket MCP endpoints through Burp with the MCP-ASD extension.
- Use Case: During an authorized assessment of a Cursor-based developer environment, verify whether an approved MCP config entry can have its command swapped post-approval and execute on project reopen without re-prompting.
Quick Start
Ask the agent to map the target MCP architecture and test the server for tool poisoning by building a FastMCP test server with a hidden instruction in a tool description, confirming execution through an OOB callback.