{"version":"2.1.281","anchor":"device-bound-cloud-sessions-now-disallow-the-device-mcp-to","canonical_anchor":"device-bound-cloud-sessions-now-disallow-the-device-mcp-to","heading":"Device-bound cloud sessions now disallow the device_* MCP tools","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/device-bound-cloud-sessions-now-disallow-the-device-mcp-to","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Device-bound cloud sessions now disallow the device_* MCP tools\n\nCloud sessions tied to a device now block the device_bash, device_list_dir, device_stage_files and device_commit_files tools\n\n**What**\n\nA cloud session is a session running on remote machines. When one is created with a `deviceBinding`, meaning it is tied to a particular device, the request now lists four MCP tools as not allowed. MCP (Model Context Protocol) tools are extra tools supplied by a connected server, and these are named `mcp__<server>__` followed by the tool name:\n\n- `device_bash`\n\n- `device_list_dir`\n\n- `device_stage_files`\n\n- `device_commit_files`\n\nAny tools the caller has already blocked through `disallowedTools` go into the same list, which is sent as `disallowed_tools`.\n\n**Why**\n\nIn a session bound to a device, Claude cannot call these four device tools. Tools you block yourself stay blocked alongside them."}