MCP Server Pentesting
Penetration testing of Model Context Protocol servers and agent tool integrations before they get production credentials.
What I deliver
- Tool description review for poisoning
- Scope and permission review per tool
- Rug-pull and version-change detection
- Tool shadowing across multiple servers
- Data-flow review: untrusted input to outbound tools
Step by step
- 01
List every connected MCP server and tool
- 02
Read tool descriptions for poisoning
- 03
Check scopes and credentials
- 04
Test tool shadowing and rug-pulls
- 05
Pin, hash and monitor definitions
Selected engagements
From my work at BERRY9 IT Services, as a freelancer, at CRIS InfoTech and Hacktr Technologies, and my own tools and research.
MCP server reviews at CRIS InfoTech — tool descriptions, scopes and data flows checked before production use
Top bugs I hunt — and the steps
The recurring weaknesses I see in this domain, with the repeatable workflow I run from discovery to fix.
- STEP 1Read every tool description the model will see
- STEP 2Look for hidden instructions or exfil requests
- STEP 3Test how the agent behaves with the server connected
- STEP 4Fix: review, pin and hash tool definitions