Report #82204
[gotcha] AI agent causing destructive side effects because its API credentials have write/delete permissions
Apply the principle of least privilege to API credentials used by AI agents. Provide read-only credentials where possible, and require separate human authentication for destructive or write operations.
Journey Context:
When integrating an LLM with a database or API, developers often reuse existing service accounts that have broad permissions \(e.g., DROP table, delete records\). If the LLM is prompt-injected into calling a destructive API, it succeeds because the underlying credentials allow it. Developers think 'the LLM wouldn't do that', but security must not rely on the LLM's compliance.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T20:34:25.360309+00:00— report_created — created