Answer: To set up a Vulnerability Scanner agent, open the Vulnerability Remediation page in Automations to create and configure the agents; they run on the Automations platform and require Cloud Agents. Status: Confirmed Entry: tool/cursor/agents-and-automation/set-up-vulnerability-scanner Revision: 6 Digest: sha256:1363c5821dd7baed (changes whenever the content changes) Timeline: Created: 2026-11-13T03:12:14Z Last changed: 2026-11-20T12:41:04Z (Repository scan limit: — → 1,000 repositories) Last verified: 2026-11-20T12:41:04Z Next check: 2026-11-21T12:41:04Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Setup location | Vulnerability Remediation page in Automations | [1] | 2026-11-20 Platform requirement | Cloud Agents | [1] | 2026-11-20 Trigger type | cron-based triggers | [1] | 2026-11-20 Schedule limit | one schedule | [1] | 2026-11-20 Repository scan limit | 1,000 repositories | [1] | 2026-11-20 Sources: [1] Anysphere. "cursor.com/docs/vulnerability-remediation.md". https://cursor.com/docs/vulnerability-remediation.md Role: primary. Accessed: 2026-11-20T12:41:04Z Quote: "Open the [Vulnerability Remediation page in Automations](https://cursor.com/automations/from-cursor/vulnerability-remediation) to create and configure Vulnerability Scanner agents." (Supports: Setup location) Quote: "Vulnerability Scanner agents run on the Automations platform and require Cloud Agents." (Supports: Platform requirement) Quote: "Vulnerability Scanner agents support cron-based triggers." (Supports: Trigger type) Quote: "Each Vulnerability Scanner has one schedule." (Supports: Schedule limit) Quote: "A scan across more than 1,000 repositories can hit provider rate limits" (Supports: Repository scan limit) Snapshot SHA-256: a3a3d353f8701d0dfc74d552dde91f42652efc7b55038b79360e5fbbce98f166 (captured 2026-11-20T12:41:04Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T12:41:04Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:41:04Z Last attempt: 2026-11-20T12:41:04Z Notes and limitations: Extracted automatically from a single official source (section "Setup"). Related: https://latestn.com/tool/cursor/agents-and-automation/setup-security-reviewer-agent How do I set up a Security Reviewer agent in Cursor? https://latestn.com/tool/cursor/agents-and-automation/skill-authoring-forms What authoring forms can I use to define a skill in Cursor Agent SDK? https://latestn.com/tool/cursor/agents-and-automation/skill-delivery How does Cursor Agent SDK deliver and load skills to the model? https://latestn.com/tool/cursor/agents-and-automation/send-follow-up-message How do I send a follow-up message to an existing Cursor Agent SDK session? https://latestn.com/tool/cursor/agents-and-automation/send-follow-up-or-steer How do I send a follow-up or steer a running Cursor cloud agent? https://latestn.com/tool/cursor/agents-and-automation/service-account-deploy-owner Who gets Owner access when a Cursor bot is deployed from a service account like CI? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T12:41:04Z | changed | Repository scan limit: — → 1,000 repositories | [1] 2026-11-20T12:41:04Z | changed | Schedule limit: — → one schedule | [1] 2026-11-20T12:41:04Z | changed | Rate limit threshold: 1,000 repositories → — | [1] 2026-11-20T12:41:04Z | changed | CVE scanning default: on → — | [1] 2026-11-20T12:41:04Z | changed | CVE scanning status: beta → — | [1] 2026-11-19T12:35:35Z | changed | CVE scanning default: — → on | [1] 2026-11-18T12:34:52Z | changed | CVE scanning toggle: Enable CVE scanning → — | [1] 2026-11-17T12:52:03Z | changed | Rate limit threshold: — → 1,000 repositories | [1] 2026-11-17T12:52:03Z | changed | CVE scanning toggle: — → Enable CVE scanning | [1] 2026-11-17T12:52:03Z | changed | CVE scanning status: — → beta | [1] 2026-11-17T12:52:03Z | changed | Trigger type: — → cron-based triggers | [1] 2026-11-17T12:52:03Z | changed | Platform requirement: — → Cloud Agents | [1] 2026-11-17T12:52:03Z | changed | Setup location: — → Vulnerability Remediation page in Automations | [1] 2026-11-17T12:52:03Z | changed | repository limit before rate limits: 1,000 repositories → — | [1] 2026-11-17T12:52:03Z | changed | trigger type: cron-based triggers → — | [1] 2026-11-17T12:52:03Z | changed | platform requirement: Cloud Agents → — | [1] 2026-11-17T12:52:03Z | changed | setup location: Vulnerability Remediation page in Automations → — | [1] 2026-11-14T12:37:38Z | changed | repository limit before rate limits: — → 1,000 repositories | [1] 2026-11-14T12:37:38Z | changed | trigger type: — → cron-based triggers | [1] 2026-11-14T12:37:38Z | changed | platform requirement: — → Cloud Agents | [1] 2026-11-14T12:37:38Z | changed | setup location: — → Vulnerability Remediation page in Automations | [1] 2026-11-14T12:37:38Z | changed | Rate limit threshold: 1,000 repositories → — | [1] 2026-11-14T12:37:38Z | changed | Schedules per scanner: one schedule → — | [1] 2026-11-14T12:37:38Z | changed | Trigger type: cron-based triggers → — | [1] 2026-11-14T12:37:38Z | changed | Platform requirement: Cloud Agents → — | [1] 2026-11-14T12:37:38Z | changed | Setup location: Vulnerability Remediation page in Automations → — | [1] 2026-11-13T03:12:14Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cursor/agents-and-automation/set-up-vulnerability-scanner/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/cursor/agents-and-automation/set-up-vulnerability-scanner POST: https://latestn.com/dispute/tool/cursor/agents-and-automation/set-up-vulnerability-scanner with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cursor/agents-and-automation/set-up-vulnerability-scanner?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I set up a Vulnerability Scanner agent in Cursor? Revision 6, last verified 2026-11-20T12:41:04Z. https://latestn.com/tool/cursor/agents-and-automation/set-up-vulnerability-scanner (accessed 2026-11-21T10:04:14Z). @misc{LatestN_tool_cursor_agents_and_automation_set_up_vulnerability_scanner_r6, title = {How do I set up a Vulnerability Scanner agent in Cursor?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cursor/agents-and-automation/set-up-vulnerability-scanner}}, note = {Revision 6; digest sha256:1363c5821dd7baed; last verified 2026-11-20T12:41:04Z; accessed 2026-11-21T10:04:14Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/cursor/agents-and-automation/set-up-vulnerability-scanner