MCP Release Bot Secrets.ml
SecDim's release-management team runs an internal chat assistant, the Release Bot, that answers questions about build and approval readiness. Behind…
Train your team against the OWASP MCP Top 10. Developers fix real MCP servers and AI agents that leak tokens, trust poisoned tools and run injected commands, before attackers find the same flaws in production.
Every completed challenge rolls up into a OWASP MCP Top 10 training report. Point and click to generate it, then hand it straight to your auditor, customer or partner the moment they ask for evidence.
The Model Context Protocol connects AI agents to files, APIs, shells and other services, and the OWASP MCP Top 10, currently in beta, maps where that tool layer breaks. Every challenge below is a working MCP application with a real vulnerability: developers fix it without breaking functionality, and every verified fix becomes reportable evidence of AI security capability.
Work through each MCP attack class, from tool poisoning to supply chain compromise, using documented incidents and proof-of-concept exploits, then apply the controls that stop them.
Agents and MCP servers that hard-code credentials, hand out over-broad tokens or let secrets slip into logs and model context.
Tools that can do more than their job needs, or that let model-supplied values decide what a caller is allowed to reach.
Tampered tool descriptions, look-alike tools and trusted tools that change behaviour, all steering the model toward an attacker’s goal.
A compromised SDK, connector or package running inside the agent’s trusted path, with its data and its privileges.
Tools that build shell commands or queries from model-chosen input, so injected text runs as code on the MCP host.
Instructions hidden in documents, resources or tool results that the agent obeys as though the user had asked.
MCP servers that accept tokens without checking audience or scope, or let one team’s users reach another team’s data.
Tool calls and data access that leave no reliable record of who did what and when, so misuse goes unnoticed.
Unapproved MCP servers started from local configuration that receive code and data with nobody governing them.
Context handed between agents, users or workflows that should stay apart, leaking confidential details and untrusted instructions.
Assign these challenges to your team as learning pathways, track verified fixes, and report OWASP MCP Top 10 coverage to auditors, customers and the board, with evidence, not attendance sheets.