Subscriptions Permissions for Connections
Part of the MountDev Ops Subscriptions documentation. Updated November 14, 2026
MountDev Ops Subscriptions documentation | Updated November 14, 2026
These are the permissions a connection can hold in Subscriptions. Each one is a single action. Pick only what the connection needs. A connection acts as the member who made it and never does more than that member could.
| Permission id | Level | What it does | Inputs |
|---|---|---|---|
subscriptions.catalog_list | Read | See the services your clients can see under Services | none |
subscriptions.catalog_save | Write | Add a service to the catalog, or change one (a new or agent-saved service starts Off) | id, name (required), description, product_id (required), page, module_id, report_id |
See the Services Your Clients Can See Under Services
Permission subscriptions.catalog_list | Read | MCP tool subscriptions_services_catalog_list (action subscriptions.services_catalog.list)
POST /account/api/v1/actions/subscriptions.catalog_list
{}Add a Service to the Catalog, or Change One (a New or Agent-Saved Service Starts Off)
Permission subscriptions.catalog_save | Write | MCP tool subscriptions_services_catalog_save (action subscriptions.services_catalog.save)
POST /account/api/v1/actions/subscriptions.catalog_save
{"name":"Example","product_id":1}