Check tool access with notion-get-tool-access
By Steven Van ·
A new MCP tool reports which Notion tools and parameters a workspace's plan restricts, so agents can check before calling them.
Notion MCP has a new notion-get-tool-access tool that reports which tools work on a connection's plan. Calling it with an empty object returns the full current_tool_access map, and an optional tool_names array such as ["search", "ai_search"] narrows the result to just those tools. It's meant to be called before using a tool whose availability depends on the plan, such as choosing between notion-search and notion-ai-search, and the result can be reused across multiple tool checks rather than looked up one at a time. The call only reads connection metadata: it doesn't grant access or change the workspace.
Entries in the map can now include restricted_parameters, listing a parameter path such as filters.title_only alongside the reason it's unavailable. A restriction can apply even when the entry's overall status is available, so a workspace can support filters.teamspace_ids for a single teamspace while restricting it for multiple teamspaces. When ai_search is exposed and available, the map leaves out search entirely, even if it's requested by name; otherwise it can list both an available search entry and an unavailable ai_search entry.