{"version":"2.1.309","anchor":"mcp-tools-expose-openworldhint","canonical_anchor":"mcp-tools-expose-openworldhint","heading":"Claude Code now reads the openWorldHint that MCP tools declare","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/mcp-tools-expose-openworldhint","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Claude Code now reads the `openWorldHint` that MCP tools declare\n\nClaude Code now passes along the `openWorldHint` an MCP server sets on a tool, as well as its read-only and destructive hints\n\n**Unclear.** What Claude Code does with `openWorldHint` once it reads it is not stated.\n\n**What**\n\nMCP servers are outside services that give Claude extra tools. A server can attach hints to each tool describing how it behaves. Claude Code already read the `readOnlyHint` and `destructiveHint` hints. It now also passes along `openWorldHint`.\n\nThe information Claude Code's automatic permission classifier receives about a tool is now built from that tool's own name. The classifier is the part that decides whether an action can go ahead without asking you.\n\n**Why**\n\nThe extra hint can feed into permission decisions, including the automatic ones.\n\n- Area: MCP\n- Names: `openWorldHint`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}