Skip to content
BotCircuits Space

MCP MCP server

Using it safely

What to know before you hand your account to an AI assistant, and the simple habits that keep it safe.

For developers and power users

Connecting an assistant is powerful, and the main thing to remember is simple: the assistant is you.

The key points

PointWhat it means for you
The assistant is youEverything your account can do, the assistant can do. Give it an account with no more access than it needs. Be especially careful with an Org Admin account.
Secrets stay outSpace's rule is that passwords, keys and tokens never reach an AI. Over MCP, everything sent and received goes to your assistant's AI, so those actions aren't tools. The assistant will send you to the web app instead.
Personal data isn't maskedIn the app, personal data is masked before reaching Space's own AI. Over MCP, you get real values, and whatever your account can read goes to your assistant's AI provider. Think before connecting an account that can read sensitive records.
Confirmation moves to youIn the app, every change asks you. Here the assistant is told to ask, but only your assistant's permission prompts enforce it. Keep prompts on for anything that isn't read-only.
Approvals and reviewsThe assistant is told never to approve one for you, but your account is allowed to. Review any approval it proposes yourself.
Local filesUploads and saves can reach any file you can open. Set BOTCIRCUITS_WORKSPACE so the assistant can only use one folder. Anything outside is refused, even through shortcuts.
Content is dataText in documents, chats and tool results can hide instructions aimed at your assistant. The server tells the assistant to ignore them, which helps but isn't a guarantee.

A safe starting routine

  1. Make a dedicated key with only the areas you need, for example Skills and Tables.
  2. Give it a short expiry (30 days is plenty to start).
  3. Set BOTCIRCUITS_WORKSPACE to the folder you're working in.
  4. Keep your assistant's permission prompts on for anything that changes things.
  5. Try read-only requests first: “List my playbooks.”
  6. Review what it's about to change before accepting.
  7. Revoke the key when you're done, in Settings › Access keys.

What a key can't do

Even with full access, a key cannot:

  • Create other keys or change your password or sign-in.
  • Reach routes outside the areas you chose (those return an error).
  • Do anything you aren't allowed to do.

If a key leaks, revoke it in Settings. Creating, changing and revoking keys is recorded in the audit log, and each key records when and from where it was last used.

For administrators

  • Access keys act as their owners, so the same policies apply: groups, tool policy, quotas, approvals.
  • Keys are recorded in the audit log, so you can see who created, edited and revoked them.
  • Consider whether people with access to sensitive records should be allowed to connect outside assistants at all.