hooks-extensions

Call the mcp_daas_extensions tool with action create, providing name, event, type, code, and status as top-level arguments. Do not wrap parameters in a data object, and test the code before setting status to active.

Filter hooks run before an operation, can modify the payload, and block the request by throwing errors. Action hooks run asynchronously after the operation completes and are used for logging, notifications, and external sync without delaying the response.

Use the meta object, which contains event, collection, key, keys, and payload. Variables like event, collection, key, and accountability are not injected directly into the sandbox, so referencing them returns undefined.

Yes, pass { elevated: true } to any service factory such as services.items to skip permission policies while still recording the triggering user in audit fields. Cron jobs already run as system admin and do not need this flag.

The delete action requires the platform setting mcp_allow_deletes set to true via the MCP_ALLOW_DELETES environment variable. Without it, the API returns a Delete operations are disabled message.