Terminal
Terminal/Skill
Shows who can see an ImageKit file, folder, or collection, and grants or removes READ, CONTRIBUTE, or MANAGE access.
By ImageKit
Works with
npx skills add imagekit-developer/skills --skill asset-access-controlUse the DAM MCP tools. Two surfaces — do not mix their tools.
| Target | Read ACL | Write ACL |
|---|---|---|
| File or folder | get_asset_access_list | update_asset_acl |
| Media collection | get_collection_access_list | update_media_collection (acl) |
list_associated_media_collections only answers "which collections contain this file/folder?". It does not change membership; use add_assets_to_media_collection / remove_assets_from_media_collection.
Restricted users can only change access on assets they can manage.
search_media_library if you only have a name or path.userId / groupId from that response — never invent ids.get_asset_access_list also returns users and userGroups for the account. Match the person the user named against userName / userEmail / label.
update_asset_aclacl.addOrModify and acl.remove. Use [] on the unused side.entity.type is only USER or USER_GROUP. MEDIA_COLLECTION may appear on read (inherited membership); do not send it on write.{
"assetId": "<file-or-folder-id>",
"acl": {
"addOrModify": [{ "entity": { "id": "<userId>", "type": "USER" }, "permission": "READ" }],
"remove": []
}
}
list_associated_media_collectionspermission is a string, not an array. Send '["MANAGE"]' or '["READ","CONTRIBUTE"]'. Omit it unless you are filtering for a restricted user.