Critical-risk tools in Courier
15 of the 123 tools in Courier are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
cancel_automationDestructiveCancel a running automation by its cancelation_token. This invokes a second ad-hoc automation with a single cancel step. The token must match the cancelation_token set when the ...
-
cancel_messageDestructiveCancel a message that is currently being delivered. Returns the message details with updated status.
-
cancel_notification_submissionDestructiveCancel a notification template submission.
-
delete_audienceDestructiveDelete an audience by its ID.
-
delete_brandDestructiveDelete a brand by its ID.
-
delete_listDestructiveDelete a list by its ID.
-
delete_profileDestructiveDelete a user profile permanently.
-
delete_providerDestructiveDelete a provider configuration. Returns 409 if the provider is still referenced by routing or notifications.
-
delete_tenantDestructiveDelete a tenant by its ID.
-
delete_tenant_preferenceDestructiveRemove default notification preference for a topic from a tenant.
-
delete_tenant_templateDestructiveDelete a tenant notification template. Returns 204 on success, 404 if the template does not exist for this tenant.
-
delete_user_list_subscriptionsDestructiveDelete all list subscriptions for a user.
-
delete_user_tokenDestructiveDelete a specific push token for a user.
-
remove_all_user_tenantsDestructiveRemove a user from all tenants.
-
remove_user_from_tenantDestructiveRemove a user from a tenant.
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.