{"found":true,"collection":"patterns","library_url":"https://www.grokbotdb.com/library/pat.per-agent-tool-restriction","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.per-agent-tool-restriction","name":"Only one agent in the pipeline ever holds a sending tool","category":"safety","problem":"Every Bot in an outbound pipeline can technically reach every connector on the account.","technique":"Keep research and qualification read-only, and give a sending tool to exactly one agent. Enforce with scoped credentials plus written boundaries, since the platform cannot enforce it.","why_it_works":"It reduces the number of places an irreversible action can originate from many to one.","when_to_use":"Outbound, support, publishing.","manual_ref":"6.2","evidence":"documented","source_url":"https://github.com/novusordos666/grokbot-outreach-agent-team","related":["pat.scoped-service-accounts","pat.bots-draft-humans-send","pat.bots-are-not-a-security-boundary"],"confidence":"high","first_seen":"2026-09-03","last_verified":"2026-09-03"}}