# Per-tool access map in notion-fetch self

By Steven Van · 2026-07-17

The notion-fetch MCP tool's self response now includes a current\_tool\_access map, so clients can tell before making a call which tools will actually run…

The [Notion](<https://creatorstoolbox.com/tools/notion>) MCP server's notion-fetch tool now returns a current\_tool\_access map in its self response, letting clients check before calling a tool whether it will actually run on the connected workspace's plan. Each entry reports a status of **available**, **limited\_free\_trial**, **upgrade\_required** (with an upgrade URL into the workspace's upgrade flow), or **not\_enabled**, so a client can route around tools that would otherwise just return an upgrade prompt. Details are in Notion's [guide to integrating your own MCP client](<https://developers.notion.com/page/changelog#july-17-2026>).

[![](<https://notion-demo.mintlify.app/images/og-image.png>)](<https://developers.notion.com/page/changelog#july-17-2026>)

![Notion](<https://www.google.com/s2/favicons?domain=notion.so&sz=128>)

Notion

All-in-one workspace for notes, docs, projects, and wikis — with AI built in for writing, summarizing, and organizing.

[View Notion →](<https://creatorstoolbox.com/tools/notion>)

Sources

[Original source](<https://developers.notion.com/page/changelog#july-17-2026>)

[Read Per-tool access map in notion-fetch self on Creators Toolbox](<https://creatorstoolbox.com/blog/notion-per-tool-access-map-in-notion-fetch-self>)

---
Canonical source: https://creatorstoolbox.com/blog/notion-per-tool-access-map-in-notion-fetch-self