Consultation integrations must respect the business context and the authorized product. Dedicated MCP links expose delimited reads, while categories and permissions remain separate controls.
Read-only MCP links
- Open the dedicated access configuration for the agent concerned.
- Check product scope and read permission before connecting.
- Complete OAuth login and consent yourself with the intended client, keeping each agent’s identity distinct.
- Consider dedicated tools as pipeline reads: they do not approve, send, or modify records.
Permissions and categories: separate controls
- Open the user profile or access configuration you want to evaluate.
- Check effective rights and business context before associating categories with records.
- Use categories to classify work, keeping permissions as a reference for access.
- When an agent’s perimeter changes, recheck the expected enablement instead of assuming it remains valid.
Putting this into practice
When preparing a link, check the profile, product and accessible information. A useful category for classification does not replace verification of user rights.
Learn more about CRM AI Pro.
Comments and questions
Do you have a question about this topic? Open the discussion with a comment.