{"version":"2.1.309","anchor":"permission-checks-ccr-cloud-browser-floor-and-hook-allow-ha","canonical_anchor":"permission-checks-ccr-cloud-browser-floor-and-hook-allow-ha","heading":"Plugins can only tighten permission for cloud browser calls","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/permission-checks-ccr-cloud-browser-floor-and-hook-allow-ha","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Plugins can only tighten permission for cloud browser calls\n\nPlugins can now only make cloud browser calls stricter, and some MCP tool asks keep their safety prompt and default to No\n\n**Unclear.** When the host-card denial in `bypassPermissions` mode applies is not clear.\n\n**What**\n\nPermission handling changed in three places:\n\n- A plugin can now only make a call to the cloud browser in remote sessions (CCR) stricter, never looser.\n\n- MCP tools whose strictest allowed setting is to ask now keep a safety check that only a person can answer, along with the `defaultToNo` setting, so the prompt starts on No.\n\n- In `bypassPermissions` mode, where Claude Code normally skips permission prompts, a new path can still deny a call on the host card.\n\n**Why**\n\nThese change how permission prompts behave for the cloud browser and when permissions are bypassed. Some calls that used to go through may now be blocked or need a person to approve them.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}