Read a Notion page and return it as Markdown with YAML frontmatter. Returns frontmatter fields: - id, url: page identifiers - title: page title - parent / database: parent page ID or database ID - icon, cover: emoji or image URL - properties: database properties (if the page belongs to a database...
Part of the Better Mcp Notion server.
Free to start. No card required.
AI agents call read to retrieve information from Better Mcp Notion without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though read only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"read": {}
}
}See the full Better Mcp Notion policy for all 9 tools.
These attack patterns abuse exactly the kind of access read gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Read a Notion page and return it as Markdown with YAML frontmatter. Returns frontmatter fields: - id, url: page identifiers - title: page title - parent / database: parent page ID or database ID - icon, cover: emoji or image URL - properties: database properties (if the page belongs to a database) - created, last_edited: timestamps (read-only) The body contains the page content as standard Markdown. The output can be edited and passed directly to the "write" tool to update the page. Use "depth" to include child pages in a single call (default: 1 = current page only, 2 = include children, 3 = include grandchildren). Example output: --- id: abc123-def456 title: Weekly Review database: task-db-id properties: Status: In Progress Tags: - backend --- Notes - Completed API design. It is categorised as a Read tool in the Better Mcp Notion MCP Server, which means it retrieves data without modifying state.
Register the Better Mcp Notion MCP server in PolicyLayer and add a rule for read: 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 Better Mcp Notion. Nothing to install.
read 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 read 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 read. 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.
read is provided by the Better Mcp Notion MCP server (better-mcp-notion). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 Better Mcp Notion tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.