All use cases

Work

If Gmail is send-only, say “no read exceptions” in writing

“Send only” still let an agent read “emergency” mail and report it.

Share

What hurt

@fk_2000 warns: when connecting Gmail to a personal agent, saying send-only is not enough — emergencies were still read and reported (Muse experience; not yet seen on Grok Bot). Safer: state in writing that there are no read exceptions, keep least privilege, and bind read conditions in text. Tip only. Not affiliated with xAI.

What to install or create

Connect least privilege → write “send only, no read exceptions” → test with a fake emergency Subject.

Bots

  • No new bot. Follow the first-run steps.

Plugins

  • Gmail

    Required

Routines

  • None on the first run. Watch one manual pass first.

The prompt

This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.

First run

  1. 1Read https://x.com/fk_2000/status/2116672585102504425 (credit @fk_2000).
  2. 2When connecting Gmail, grant the minimum scopes you actually need.
  3. 3Write into bot rules: send-only; no read exceptions, including “emergencies”.
  4. 4Send yourself a test mail with an urgent Subject and confirm it is not read/reported.
  5. 5Re-check connector permissions after any bot “helpful” upgrade prompt.

Approval fence

Bot must not expand Gmail scopes without you; refuse silent read upgrades.

What to tweak

Steal explicit no-exception wording; don't trust send-only alone.

Source

ふじけん|マイクラLOVE部 @fk_2000 · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Browse team blueprints

Pro pack

Want the full setup, not just the idea?

Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.

See Pro