notion_open_page
Opens a Notion page in the desktop app (deep link). Accepts a page id or title. Useful to let the user view or edit a page, or to pull an uncached page into the local cache.
This record as markdown: /tools/com-local-mcp-local-mcp/notion-open-page.md
What notion_open_page does on Local
AI agents invoke notion_open_page to trigger actions in Local. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | string | Yes | Page id (UUID) or title (partial, case-insensitive) |
Parameters from the server's own tool schema.
Why notion_open_page is rated High
This tool triggers an external operation — launching/opening the Notion desktop application via a deep link. It doesn't just read data; it actively causes an application to open and navigate to a specific page. While it has a read-like intent (viewing a page), the mechanism is executing an external action (deep link invocation).
From the tool's definition Opens a Notion page in the desktop app (deep link)
Attacks that exploit this kind of access
The rule that runs notion_open_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_open_page, this is the rule to start with:
notion_open_page stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_open_page call is checked against it from then on.
Questions about notion_open_page
Opens a Notion page in the desktop app (deep link). Accepts a page id or title. Useful to let the user view or edit a page, or to pull an uncached page into the local cache. It is categorised as a Execute tool in the Local MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
notion_open_page accepts 1 parameter: page. 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_open_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_open_page is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the notion_open_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_open_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_open_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.
Across the catalogue