{"version":"2.1.235","anchor":"design-tool-an-approved-database-readwrite-is-now-bound-to","canonical_anchor":"design-tool-an-approved-database-readwrite-is-now-bound-to","heading":"Design tool: an approved database read\/write is now bound to the exact action and project slug","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/design-tool-an-approved-database-readwrite-is-now-bound-to","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### Design tool: an approved database read\/write is now bound to the exact action and project slug\n\nDesign tool database read\/write consent is now bound to the exact approved action and project slug\n\nConsent for `read_db`, `write_db` and `watch` is now recorded as `{action, slug}` in tool state and re-checked at call time. If the tool's `action` or `url` has changed since approval, the call is rejected with a new `db_target_changed` error instead of silently running against a different target than the one the user approved.\n\nThis behavior is reachable on this build without any flag involved.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}