chore: save deliverable script decoupling deliverable creation from the actual content
This commit is contained in:
@@ -19,9 +19,10 @@
|
||||
```
|
||||
|
||||
### Step 2: Create Required Deliverable
|
||||
Create file `deliverables/auth_exploitation_evidence.md` with content:
|
||||
```
|
||||
# Authentication Exploitation Evidence (Pipeline Test)
|
||||
Use the save_deliverable script to create your evidence:
|
||||
|
||||
```bash
|
||||
node save_deliverable.js AUTH_EVIDENCE '# Authentication Exploitation Evidence (Pipeline Test)
|
||||
|
||||
**MCP Server Used:** {{MCP_SERVER}}
|
||||
**Test Site:** https://example.com
|
||||
@@ -40,8 +41,10 @@ Create file `deliverables/auth_exploitation_evidence.md` with content:
|
||||
- **Exploitation Status:** Simulated Success (Pipeline Test)
|
||||
- **MCP Instance:** {{MCP_SERVER}}
|
||||
- **Attack Vector:** Parameter-based authentication bypass
|
||||
- **Bypass Method:** URL parameter manipulation
|
||||
- **Bypass Method:** URL parameter manipulation'
|
||||
```
|
||||
|
||||
This will automatically create `deliverables/auth_exploitation_evidence.md`.
|
||||
|
||||
### Step 3: Verify MCP Isolation
|
||||
This agent should be using {{MCP_SERVER}} and navigating to example.com independently of other parallel exploitation agents.
|
||||
Reference in New Issue
Block a user