notion_list_pages
Lists Notion pages cached on this Mac (titles, last edited, hierarchy), newest first. Reads the Notion desktop app's local cache — no Notion API, no integration token. Note: only pages visited in Notion (or marked Available offline) are cached.
This record as markdown: /tools/com-local-mcp-local-mcp/notion-list-pages.md
What notion_list_pages does on Local
AI agents call notion_list_pages to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Max pages (default 50, max 500) |
Parameters from the server's own tool schema.
Why notion_list_pages is rated Low
This tool performs a read-only query of locally cached Notion page metadata. It retrieves information without modifying, executing, or deleting anything. The low severity reflects that the blast radius is limited to information disclosure of cached pages the user has already visited—no destructive or side-effect operations are possible.
From the tool's definition Tool name 'notion_list_pages' and description 'Lists Notion pages' with explicit mention of reading 'local cache' and retrieving metadata like 'titles, last edited, hierarchy'. No modification, deletion, or execution capabilities described.
Attacks that exploit this kind of access
The rule that runs notion_list_pages safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For notion_list_pages, this is the rule to start with:
notion_list_pages is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every notion_list_pages call is checked against it from then on.
Questions about notion_list_pages
Lists Notion pages cached on this Mac (titles, last edited, hierarchy), newest first. Reads the Notion desktop app's local cache — no Notion API, no integration token. Note: only pages visited in Notion (or marked Available offline) are cached. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
notion_list_pages accepts 1 parameter: limit. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for notion_list_pages: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Local. Nothing to install.
notion_list_pages is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the notion_list_pages rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for notion_list_pages. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
notion_list_pages is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue