{"version":"2.1.318","anchor":"host-declared-peer-messages-carrying-disallowed-tools-are-re","canonical_anchor":"host-declared-peer-messages-carrying-disallowed-tools-are-re","heading":"Messages from another session that try to block tools are refused","tier":"notice","area":"Peer Sessions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/host-declared-peer-messages-carrying-disallowed-tools-are-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Messages from another session that try to block tools are refused\n\nA message from a declared peer session that includes a disallowed_tools list is now refused instead of accepted\n\n**What**\n\nClaude Code sessions can receive messages from other sessions, called peers. A peer that a host session has declared can no longer send a message that includes a `disallowed_tools` list, which names tools to block. Claude Code refuses such a message and logs an error. This reason is checked before the other reasons for refusing a message.\n\n**Why**\n\nA peer's turn cannot apply a list of blocked tools. Refusing the message stops a block from appearing to be in place when it would be ignored.\n\n- Area: Peer Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}