{"version":"2.1.271","anchor":"new-appliesmodedrop-1-escape-hatch-for-mode-based-tool-r","canonical_anchor":"new-appliesmodedrop-1-escape-hatch-for-mode-based-tool-r","heading":"New appliesModeDrop: !1 escape hatch for mode-based tool restriction, unused","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/new-appliesmodedrop-1-escape-hatch-for-mode-based-tool-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### New `appliesModeDrop: !1` escape hatch for mode-based tool restriction, unused\n\nA new but currently unused `appliesModeDrop: false` option can bypass mode-based tool restrictions\n\n**Unclear.** The finding doesn't show anything actually setting `appliesModeDrop` to false, so it's unclear what currently uses this escape hatch.\n\n**What**\n\nThe same tool-restriction logic that decides which tools get cut based on the current mode now has an escape hatch: if a new options field called `appliesModeDrop` is explicitly set to `false`, no restriction is applied at all, alongside the existing exemptions for things like `plugin_install_diff` and `plugins_sync`.\n\n**Why**\n\nThis adds a way to opt specific cases out of mode-based tool restriction, though nothing yet appears to set this option, so it has no visible effect for users right now.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}