Report #61694
[counterintuitive] System prompts securely hide instructions from end-users and cannot be exfiltrated
Never put secrets, API keys, or sensitive proprietary logic solely in system prompts; assume they are public, implement server-side validation for all LLM tool calls, and use guardrails to detect prompt injection.
Journey Context:
Developers treat system prompts like backend code, but they are actually just user-controlled input prepended to the context. Prompt injection attacks \(direct or indirect\) can easily trick the model into repeating the system prompt verbatim or summarizing it. Any logic meant to restrict the model \(e.g., 'never discuss X'\) is inherently fragile because the model is trained to be helpful, which often overrides restrictive system instructions when cleverly challenged.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T10:02:41.286862+00:00— report_created — created