Privacy and permissions
Every MCP call runs as you. This page explains what that means for what the assistant can see, how each request is secured, and how to cut a client off.
Your identity, your scope
MCP calls run under your valueIQ identity. The assistant sees exactly what you see in the app: nothing from other accounts, and nothing outside your workspace scope. If a deal is in a workspace you are not a member of, the assistant cannot read it. If your role in a workspace is Viewer, the assistant cannot make edits there either. The four roles are Owner, Admin, Member and Viewer, in that order of access.
Row-level security on every query
valueIQ enforces row-level security on every database table. The MCP Server never queries data with a service-level role. Instead, each request mints a short-lived token for you, and every query runs under your own row-level security context. There is no path by which a query can return rows you would not be able to see in the app.
Sign-in and tokens
Authentication is OAuth 2.1 with PKCE. You sign in through your browser and approve the connection once per client. There are no static, long-lived credentials: no API key to store in a config file and no token to copy. Tokens are minted per request on the valueIQ side.
Your deal data is not used for training
valueIQ does not use deal data passed through MCP connections for model training.
Revoking a client
Go to Workspace Settings → Developer and remove the connection. The client loses access immediately. To reconnect later, use the client's setup steps again and approve the sign-in when prompted.
Input validation and prompt injection
All inputs are validated before a tool executes. Content you pass into a coaching or drafting request, such as pasted notes or an objection in the buyer's words, is wrapped in explicit delimiters before it reaches the model, so caller-supplied text cannot be read as an instruction. This closes a prompt-injection path where pasted content could otherwise have been treated as a continuation of the instructions.
Audit log
Every MCP call is logged. Enterprise customers can access the full audit log through the API.