{"found":true,"collection":"patterns","library_url":"https://www.grokbotdb.com/library/pat.no-credential-the-roster-should-not-have","generated":"2026-09-06T05:32:11Z","citation":["Quote the record id and its source_url (or provenance if there is no URL).","Include last_verified or observed_at when present. Do not present an old date as current.","If tier is community and confidence is low, say so. Do not launder it into a fact.","If the database does not hold the answer, say that. Do not invent Grok Bot product claims.","Contradictions are data: when conflicts_with is present, report both records rather than picking a favourite.","Deprecated and removed records stay visible. They are history, not current guidance."],"record":{"id":"pat.no-credential-the-roster-should-not-have","name":"Nothing on the computer that the whole roster should not hold","category":"safety","problem":"A credential or file dropped in for one Bot is available to every Bot, forever.","technique":"Before placing a credential or a sensitive file on the shared computer, ask whether every Bot you will ever create should be able to use it. If not, it does not go there.","why_it_works":"The account, not the Bot, is the boundary.","when_to_use":"Every connection and every file drop.","manual_ref":"1.2","evidence":"documented","source_url":"https://docs.x.ai/grok-bot/faq","related":["pat.bots-are-not-a-security-boundary","pat.scoped-service-accounts"],"confidence":"high","first_seen":"2026-09-03","last_verified":"2026-09-03"}}