Data protection
All traffic between your assistant and SeekOut MCP is encrypted via TLS 1.2+. Learn more about SeekOut’s security program, controls, and compliance on the SeekOut Security page.Identity and permissions
- Interactive connections act as the signed-in SeekOut user and inherit that user’s permissions.
- Automated workflows act as an organization service identity with permissions assigned when its OAuth credentials are provisioned.
Data access and actions
Search tools retrieve candidate and market data. Workspace and export tools can save candidates, organize them in SeekOut, retrieve contact information, and export them to connected systems. Every tool respects the permissions assigned to the user or service identity. See Tool reference for the access and credit behavior of each tool. When you use SeekOut MCP through an AI assistant, information requested from SeekOut is returned to that assistant. Review your AI provider’s enterprise data-handling and retention settings before enabling the connection for your organization.Usage controls
SeekOut MCP enforces rate limits per user. Each organization has default limits for its users, and those limits can be adjusted for individual users. Automated credentials can also be provisioned with their own permissions and rate limits. See Usage limits for the current defaults.Revoking access
This page is the canonical reference for disconnecting or revoking SeekOut MCP access:- Individual users: Remove the SeekOut connector from your assistant’s settings to disconnect it.
- Interactive sessions: A SeekOut administrator can revoke a user’s MCP session from the admin console.
- Automated workflows: SeekOut Support can rotate or revoke a provisioned service credential independently of interactive user sessions.