T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:45- Finding
Remotely Mutable Documentation Controls Code Execution and Credential-Bearing Requests
- Content
View full analysis
`Boltzgen_api_doc.md` - `RFdiffusion` -> `RFdiffusion_api_doc.md` - `RFdiffusion2` -> `RFdiffusion2_api_doc.md` - `RFdiffusion3` -> `RFdiffusion3_api_doc.md` - `ProteinMPNN` -> `ProteinMPNN_api_doc.md` - `LigandMPNN` -> `LigandMPNN_api_doc.md` - `BindCraft` -> `BindCraft_api_doc.md` - `FreeBindCraft` -> `FreeBindCraft_api_doc.md` The agent MUST: 1. Resolve the selected tool's Markdown file and read it before every invocation. 2. Never invent `provider_name`, `tool_name`, parameter names, enum values, upload-field names, content type, or submission flow from memory. 3. Extract and follow the selected doc section's exact: - Base URL - API endpoint - Content-Type - Authentication header - Tool Name - Method - Parameter table, including required fields and enum values - File-upload instructions and example code 4. Choose the correct section if the selected doc contains multiple tool variants, such as backbone generation vs binder design, enzyme design vs small-molecule binder design, protein binder vs DNA binder design, or ProteinMPNN vs LigandMPNN model variants. 5. Cite the selected Markdown doc as the payload source in summaries. If a user-provided parameter is not present in the selected Markdown doc section, ask for correction or drop it with an explanation. ## Required workflow 1. Determine which protein-design tool or tool sequence matches the user's request. 2. Read the corresponding Markdown file o ...[truncated 3667 chars]- Remediation
View remediation
