Project scoping and privacy
When you connect an AI client, Spiderlook scopes tools to the project you authorize.
How does project scope work?
OAuth consent selects the project landscape the client can read and act on. Other organizations and projects stay out of that connection. Call list_workspace in the client to see only what the signed-in user can access.
What operational care should I take?
Only invite trusted teammates and connect clients you control. Revoke unused connectors from the AI agents panel when someone leaves. Prefer Ask Spidey for quick in-app questions when you do not need an external client.
Write tools such as add_competitor or generate_battlecard can change the project and may use extra allowance — treat MCP write access like in-app admin rights.