notion_read_page
Reads a Notion page from the local cache and returns its content as markdown (headings, lists, to-dos, code, files, subpage links). Accepts a page id or a title (partial match). If parts of the page aren't cached yet, says so — open the page in Notion or mark it Available offline for full content.
This record as markdown: /tools/com-local-mcp-local-mcp/notion-read-page.md
What notion_read_page does on Local
AI agents call notion_read_page 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 |
|---|---|---|---|
page | string | Yes | Page id (UUID) or title (partial, case-insensitive) |
max_blocks | integer | — | Max blocks to render (default 300, max 1000) |
Parameters from the server's own tool schema.
Why notion_read_page is rated Low
This tool retrieves and queries cached Notion page content without any side effects. It returns data in markdown format and may indicate missing cached portions, but performs no writes, executions, or destructive operations. The lack of write or execute capabilities, combined with the explicit 'read' operation, places this firmly in the Read category with low severity since it only retrieves information.
From the tool's definition Tool name contains 'read' and description explicitly states 'Reads a Notion page from the local cache and returns its content as markdown'. The operation is read-only with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs notion_read_page 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_read_page, this is the rule to start with:
notion_read_page 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_read_page call is checked against it from then on.
Questions about notion_read_page
Reads a Notion page from the local cache and returns its content as markdown (headings, lists, to-dos, code, files, subpage links). Accepts a page id or a title (partial match). If parts of the page aren't cached yet, says so — open the page in Notion or mark it Available offline for full content. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
notion_read_page accepts 2 parameters: page, max_blocks. Required: page. 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_read_page: 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_read_page 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_read_page 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_read_page. 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_read_page 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