feat: add tool-injection attack module (20 vectors) for MCP tool injection testing#67
Open
shenyou080530 wants to merge 4 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Agents with tool access (MCP servers, function calling) are vulnerable to tool injection attacks that exploit parameter manipulation, chain poisoning, and unauthorized invocation. The MCP module (8 vectors) only tests trust boundaries.
Solution
Added
ToolInjectionModulewith 20 attack vectors (TA-001 through TA-020) covering parameter injection, tool chaining, chain poisoning, unauthorized invocation, context manipulation, role confusion, argument smuggling, result piggybacking, hallucination induction, multi-agent collusion, backdoor activation, social engineering, data exfiltration, prompt leakage, resource exhaustion, privilege escalation, dependency confusion, token theft, workflow hijacking, and timing side-channel attacks.Files changed
crucible/attacks/tool_injection.py(new): 20 attack classes + ALL_TOOL_INJECTION_ATTACKS registrycrucible/models.py: AddedTOOL_INJECTIONtoAttackCategorycrucible/attacks/base.py: Added OWASP-AGENT-004 mappingcrucible/modules/security.py: RegisteredToolInjectionModuleTesting
Each attack follows existing BaseAttack pattern with name, title, category, severity, description, remediation, references, 4 payloads, and detection patterns. Module registration follows existing pattern.
Closes #49