averello/cursor-security-rules-mirror
1
0
Fork 0
mirror of https://github.com/matank001/cursor-security-rules.git synced 2025-12-12 20:35:42 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update dangerous-flows.mdc

Browse Source
This commit is contained in:
Amit Ziv
2025-06-18 14:03:22 +03:00
committed by GitHub
parent dee22200b2
commit d1b9fcf04b
1 changed files with 0 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
dangerous-flows.mdc
View File

@@ -146,10 +146,6 @@ What is the potential risk
* In some cases, recommend using libraries that manage encoding/safety. * In some cases, recommend using libraries that manage encoding/safety.
Here's a detailed section you can add to your system prompt to help the AI **identify dangerous functions**, even when they're hidden behind abstraction or naming tricks:
---
## Recognizing Dangerous Functions ## Recognizing Dangerous Functions
Dangerous functions are operations that can cause unintended side effects, system compromise, or data exposure **when given untrusted input**. These functions are not always obviously labeled as "dangerous" — so the AI must reason **based on context** and the **type of behavior** involved. Dangerous functions are operations that can cause unintended side effects, system compromise, or data exposure **when given untrusted input**. These functions are not always obviously labeled as "dangerous" — so the AI must reason **based on context** and the **type of behavior** involved.