Return an add-on to the organization's default
Removes the org's allow or forbid: the listing is then allowed, unless it is a community listing and the org has not opted in. Needs integrations.manage. Audited.
Authorization
bearerAuth A RemoteHost API key (rh_sk_...) or a user session token.
In: header
Path Parameters
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X DELETE "https://example.com/orgs/string/addons/string/policy"{ "addon": { "id": "string", "slug": "skill/code-review", "kind": "app", "name": "string", "summary": "string", "publisher": "string", "provenance": "first_party", "status": "listed", "attachLevels": [ "org" ], "pricing": "free", "iconUrl": "string", "held": true, "holding": "held_free", "policy": { "setting": "allow", "allowed": true } }}Get one add-on, with its details GET
One catalog entry, as the list shows it, and its kind's details: an MCP server's transport and tools, or a skill's package and requirements. Apps, plugins and resources have none. An alias's id (a retired slug's) answers as the entry that replaced it. A listing the caller could not see in the list is a 404 here too.
Allow or forbid an add-on in an organization PUT
`allowed: false` forbids the listing: nothing installs it, and existing installs stop being delivered. `allowed: true` allows it, even a community listing while community add-ons are off. Needs `integrations.manage` (owners and admins). Audited.