Security and Validation

The MCP Registry uses a governance-based security model to ensure that only trusted MCP servers can access your systems. This applies to both Public MCPs and Custom MCPs registered from your Artifactory.

How Security Works

Access control happens at two levels:

MCP-level: Which MCP servers are allowed in your project (governance).
Tool-level: Which specific tools within an MCP can be used (tool policies).

❗️
Important
MCP servers execute with the permissions of the user who invokes them through the MCP Gateway. This means:

Users can only access data and perform actions they are already authorized to do.

MCP servers cannot escalate privileges beyond the invoking user's permissions.

All actions are auditable and traceable to specific users.

Validation at Registration

Custom MCP servers are validated before they are added to the Registry: the package must exist in a local Artifactory repository, the repository must belong to the target project, and you must have ALLOW permission on the project and READ access to the repository. Public MCPs are scanned (e.g. for vulnerabilities and licenses) before you allow them for a project.