{"version":"2.1.300","anchor":"tool-context-accessor-expanded-with-tools-messages-mcpclie","canonical_anchor":"tool-context-accessor-expanded-with-tools-messages-mcpclie","heading":"Restricted context object exposes tools, messages and MCP clients","tier":"internal","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/tool-context-accessor-expanded-with-tools-messages-mcpclie","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Restricted context object exposes tools, messages and MCP clients\n\nA restricted context object now exposes tools, messages, the message queue, MCP clients and the permission phase, and drops file-read state\n\n**Unclear.** It is not shown whether hooks or anything else a user writes can read this object.\n\n**What**\n\nA limited view of Claude Code's internal state, already exposing `hookOrigin` and `agentContext`, now also exposes:\n\n- `tools`, the tools available\n\n- `messages` and `messageQueue`, the conversation and messages waiting to be sent\n\n- `mcpClients`, connections to MCP servers (add-ons that provide extra tools)\n\n- `teammateContext`\n\n- `permissionPhase`\n\nIt no longer exposes the record of which files have been read.\n\n**Why**\n\nThis prepares the object for new code that needs more of the session's state.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}