Cut permissions down to what the job needs
least-privilege
Name the one action, then write that the task must not do the rest. A sign-in screen is not a list of switches you can clear.
for Grok Bot · unofficial, not affiliated with xAI
CNPS0.1.02026-11-18New
Paste this note into Grok Bot and say: follow this note.
Note: Cut permissions down to what the job needs
Name the one action, then write that the task must not do the rest. A sign-in screen is not a list of switches you can clear.
For: People connecting mail, CRM, notes, a spreadsheet, or team chat.
What to check:
1. Starts from one verb: read subjects, write a draft, read one sheet tab.
2. Writes send, delete, permission changes, and payment as things this task must not do.
3. Has you write down the task rule next to what the app can do, so the next check can tell them apart.
Steps:
1. Write the action as one line with Scope list. If you cannot name a verb, do not connect yet.
2. Enable only the connector entry that matches. This version has no “entire mailbox” entry.
3. In the task, say not to send, not to delete, and not to change admin settings. The docs do not say the sign-in screen can remove those actions one by one.
4. Copy the granted scopes into the scope list, next to what the entry asked for.
Action: read the subject and sender of the last 20 messages, and draft a reply.
This task may: read mail, write a draft.
This task must not: send, delete, change the account, or read every historical attachment.
The Gmail app can send. Not sending is a task rule, not a switch on the sign-in screen.
Do not:
- Do not save a token that appears in a screenshot of a permission screen.
- Do not assume a grant is narrow when an admin setting is hidden from you.
- Do not grant send, delete, or pay for convenience.
Paste this note into Grok Bot and say: follow this note.What it does
- Starts from one verb: read subjects, write a draft, read one sheet tab.
- Writes send, delete, permission changes, and payment as things this task must not do.
- Has you write down the task rule next to what the app can do, so the next check can tell them apart.
Who it is for
People connecting mail, CRM, notes, a spreadsheet, or team chat.
How to put it in Grok Bot
- Write the action as one line with Scope list. If you cannot name a verb, do not connect yet.
- Enable only the connector entry that matches. This version has no “entire mailbox” entry.
- In the task, say not to send, not to delete, and not to change admin settings. The docs do not say the sign-in screen can remove those actions one by one.
- Copy the granted scopes into the scope list, next to what the entry asked for.
Example
One line that is enough
Action: read the subject and sender of the last 20 messages, and draft a reply.
This task may: read mail, write a draft.
This task must not: send, delete, change the account, or read every historical attachment.
The Gmail app can send. Not sending is a task rule, not a switch on the sign-in screen.Connectors it needs
No connector.
Safety and permissions
- Do not save a token that appears in a screenshot of a permission screen.
- Do not assume a grant is narrow when an admin setting is hidden from you.
- Do not grant send, delete, or pay for convenience.
Risk: Low
Questions
Can read-only still be too much?
Yes. Read one mailbox or one sheet rather than the whole organization. If the entry cannot say that, name the folder or the tab inside the skill.
Why is draft access not low?
Draft access usually comes with reading mail, and mail is private. The mail connector is medium.
0.1.0
2026-11-18
First published text. Name the action, then grant.