Read-only access to Cloudsmith packages, repositories, and audit events
Ask about an artifact and get an answer from Cloudsmith itself. Look up package metadata, checksums, and security state with CLOUDSMITH_GET_PACKAGE, scan a repository with CLOUDSMITH_LIST_REPOSITORY_VULNERABILITIES, check storage and bandwidth with CLOUDSMITH_GET_QUOTA, or trace a change through CLOUDSMITH_SEARCH_AUDIT_LOG. Connect with an API key. Access is read-only, so nothing in your repositories changes.
10 tools, all read-only. They answer instantly, and every call is logged.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
No. Every one of the 10 tools LuumenAI has for Cloudsmith is read-only, so it can answer questions from Cloudsmith but cannot change anything in it. Read actions still follow the configured access and approval policy, and are recorded on the audit trail.
You decide. Access is granted per agent, skill, and team, and per environment — production is not staging.
Every call to Cloudsmith is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.