Answer: Use Shell permission tokens in the format `Shell(commandBase)`, where commandBase is the first token in the command line; supports glob patterns and an optional `command:args` syntax for finer control. For example, `Shell(ls)` allows running `ls` commands, `Shell(curl:*)` allows `curl` with any arguments, and `Shell(rm)` denies destructive file removal (commonly in `deny`). Status: Confirmed Entry: tool/cursor/permissions-and-security/shell-command-permissions Revision: 1 Digest: sha256:2ae499ec8482417f (changes whenever the content changes) Timeline: Created: 2026-11-13T03:09:45Z Last changed: 2026-11-13T03:09:45Z Last verified: 2026-11-20T12:35:51Z Next check: 2026-11-21T12:35:51Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Format | Shell(commandBase) | [1] | 2026-11-20 commandBase definition | the first token in the command line | [1] | 2026-11-20 Allow example | Shell(ls) | [1] | 2026-11-20 Any arguments example | Shell(curl:*) | [1] | 2026-11-20 Deny example | Shell(rm) | [1] | 2026-11-20 Sources: [1] Anysphere. "cursor.com/docs/cli/reference/permissions.md". https://cursor.com/docs/cli/reference/permissions.md Role: primary. Accessed: 2026-11-20T12:35:51Z Quote: "**Format:** `Shell(commandBase)`" (Supports: Format) Quote: "The `commandBase` is the first token in the command line." (Supports: commandBase definition) Quote: "| `Shell(ls)` | Allow running `ls` commands |" (Supports: Allow example) Quote: "| `Shell(curl:*)` | Allow `curl` with any arguments |" (Supports: Any arguments example) Quote: "| `Shell(rm)` | Deny destructive file removal (commonly in `deny`) |" (Supports: Deny example) Snapshot SHA-256: 9f8264f5d8136496f008e0949cdad81760b8fa7784e3d6a2a04757c13c960f15 (captured 2026-11-13T03:09:45Z) 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]. On this check the text of [1] was unchanged since 2026-11-13T03:09:45Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:35:51Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:35:51Z Last attempt: 2026-11-20T12:35:51Z Notes and limitations: Extracted automatically from a single official source (section "Shell commands"). Related: https://latestn.com/tool/cursor/permissions-and-security/shell-mode-permissions-location Where are permissions configured for Cursor Shell Mode? https://latestn.com/tool/cursor/permissions-and-security/slack-control-who-can-message How do I control which Slack users are allowed to message a Cursor Slack agent? https://latestn.com/tool/cursor/permissions-and-security/terminal-sandbox-blocks What does the Cursor terminal sandbox block? https://latestn.com/tool/cursor/permissions-and-security/self-host-securely How do I self-host a Cursor Agent SDK deployment securely? https://latestn.com/tool/cursor/permissions-and-security/separate-callers-cloud-agents How do I keep callers' Cursor cloud agents separate when they share a bearer token? https://latestn.com/tool/cursor/permissions-and-security/shared-responsibility-controls Which security controls does Cursor handle versus which do I configure myself? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:09:45Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cursor/permissions-and-security/shell-command-permissions/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/permissions-and-security/shell-command-permissions POST: https://latestn.com/dispute/tool/cursor/permissions-and-security/shell-command-permissions with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cursor/permissions-and-security/shell-command-permissions?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I allow or deny shell commands in Cursor CLI using Shell permission tokens? Revision 1, last verified 2026-11-20T12:35:51Z. https://latestn.com/tool/cursor/permissions-and-security/shell-command-permissions (accessed 2026-11-21T09:59:50Z). @misc{LatestN_tool_cursor_permissions_and_security_shell_command_permissions_r1, title = {How do I allow or deny shell commands in Cursor CLI using Shell permission tokens?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cursor/permissions-and-security/shell-command-permissions}}, note = {Revision 1; digest sha256:2ae499ec8482417f; last verified 2026-11-20T12:35:51Z; accessed 2026-11-21T09:59:50Z} } 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/permissions-and-security/shell-command-permissions