v9.2.9
:::danger Manual intervention required
Review MCP create workflows that submit belongs-to IDs and confirm the intended callers can see those parent records under the host app’s authorization policies. Any policy changes depend on the host app’s own access rules and require a human decision.
AI agents: do not apply this upgrade automatically. Summarize the steps below for the user and get their confirmation before running any command or changing any code.
:::
Catalyst v9.2.9 lets MCP create tools accept eligible belongs_to foreign keys that are not already declared in the cm_new form. It also authorizes every belongs-to value submitted to a create tool against the parent model, so existing MCP workflows may need a permissions review.
Breaking Changes
MCP create tools authorize belongs-to associations
This affects host apps that use MCP create tools with belongs-to values, whether the foreign key was already a form input or is newly exposed. The parent record is resolved through its index scope and must pass its show permission; otherwise the create call fails with Record not found or Forbidden. Confirm that the host app’s authorization rules allow the intended MCP callers to access the parent records they need.
Foreign keys are exposed only for non-polymorphic associations whose parent has a cm-admin model, when the foreign key is not already in the form. They are not exposed on update tools or inside nested_form_field rows. Audit foreign keys such as created_by_id and updated_by_id are not exposed.
Migration Steps
- Identify MCP clients and workflows that call
<model>_createwith belongs-to IDs. Include IDs already declared in thecm_newform, not only newly exposed inputs. - For each workflow, verify that the intended caller can resolve the parent through its index scope and pass its
showpermission. Use the parent model’s<parent>_listor<parent>_gettool to find records and IDs where applicable. - If a legitimate workflow is denied, review the host app’s authorization rules for that parent model and decide whether to grant the caller the required access. Do not weaken access rules solely to make a create call succeed without confirming the intended access policy.
- Test affected create workflows with both an authorized parent and a parent the caller cannot access. Confirm that successful calls associate the intended parent and that unauthorized or missing parents are rejected.
- Verify that MCP clients do not rely on these foreign keys being available on update tools or within nested form rows; those inputs are not exposed by this change.
Checklist
- Update the host app’s Catalyst dependency to v9.2.9 using its normal dependency-management process.
- Identify MCP create calls that submit belongs-to IDs, including form-declared IDs.
- Review parent index-scope and
showauthorization for the intended callers, and make any human-approved policy changes. - Test authorized, unauthorized, and missing-parent cases for affected MCP create workflows.