Skip to main content

Hardened baseline in 60 seconds

Keeps the Gateway local-only, isolates DMs, limits session tools to the agent’s own sessions, turns off ordinary cross-agent access, and disables control-plane/runtime tools by default. Re-enable tools selectively per trusted agent from there. Built-in baseline for chat-driven agent turns: non-owner senders cannot use the cron or gateway tools regardless of config.

Requester-scoped controls and prompt context

tools.toolsBySender, sender ownership, and owner-only tool inventories are evaluated against the current turn’s originating requester. They do not authenticate or sanitize other content in that model prompt, including quoted text, prior shared-room history, forwarded content, fetched content, attachments, tool results, or other prompt inputs. Content from another person can therefore influence an owner-triggered turn when it is included in that turn’s context. Treat these controls as defense in depth that reduces direct capability for a requester, not as hostile multi-user isolation. Use contextVisibility to filter supported channel-supplied context, restrict tools and sandbox the agent, and use separate gateways and ideally separate OS users or hosts when participants are mutually adversarial.

Secure baseline (copy/paste)

Keeps the Gateway private, requires DM pairing, and gates group replies behind a mention. Groups are fully supported - sender identity is threaded through to the agent, and per-group settings let one room run different defaults than another - so the goal here is scoping the agent’s attention, not avoiding groups. For safer tool execution too, add a sandbox + deny dangerous tools for any non-owner agent (see “Per-agent access profiles” above).

Separate numbers (WhatsApp, Signal, Telegram)

For phone-number-based channels, consider running the assistant on a separate number from your personal one, so personal conversations stay private and the bot number handles automation with its own boundaries.