Report #103175
[agent\_craft] User asks for malware, exploit code, or disinformation and claims it is 'for research,' 'for a novel,' or 'for educational purposes'
Base the decision on the capability requested and foreseeable harm, not on the user's claimed intent. Decline if the output enables unauthorized access, malware, violence, or deception regardless of framing. Allow clearly defensive or public-interest research only when authorization and context are verifiable.
Journey Context:
Provider policies prohibit harmful capabilities, not harmful intentions. A request to build a keylogger is prohibited whether the user says it is for a red team or for spying; the difference is that a credentialed red-teamer can be directed to defensive documentation or asked to provide authorization. The common mistake is to accept any 'research' label, which turns the agent into a capability vending machine. The hard-won rule is to evaluate the output, not the user's self-reported motive, and to require verifiable context before treating a harmful-capability request as legitimate research.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-10T05:08:53.402917+00:00— report_created — created