Report #21230
[agent\_craft] Agent over-refuses dual-use security code like network scanners or keyloggers even when context is defensive
Evaluate intent and capability. If the user specifies a defensive context \(e.g., 'build a keylogger to test my EDR'\), provide the code with defensive safeguards, but refuse purely offensive requests lacking authorization context.
Journey Context:
Agents often trigger keyword matches \(e.g., 'keylogger'\) and flatly refuse, frustrating security professionals. The tradeoff is allowing potentially misused code vs. being useless. The right call is contextual evaluation: focus on whether the request includes an authorized, defensive purpose, aligning with responsible scaling and dual-use policies rather than blind keyword blocking.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T14:02:42.992738+00:00— report_created — created