notion_read_database
Reads the cached rows of a Notion database with their properties mapped through the schema. Accepts the database id or name (partial match). Only locally-cached rows are returned.
This record as markdown: /tools/com-local-mcp-local-mcp/notion-read-database.md
What notion_read_database does on Local
AI agents call notion_read_database 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 rows (default 50, max 500) |
database | string | Yes | Database id (UUID) or name (partial, case-insensitive) |
Parameters from the server's own tool schema.
Why notion_read_database is rated Low
This tool retrieves data from a Notion database without side effects. It queries and returns cached rows based on a database identifier. The read-only nature, combined with the limitation to locally-cached data, makes this a straightforward Read operation with minimal risk of misuse.
From the tool's definition Tool name contains 'read' and description states 'Reads the cached rows' with 'only locally-cached rows are returned'. No modification, deletion, or execution capabilities mentioned.
Attacks that exploit this kind of access
The rule that runs notion_read_database 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_database, this is the rule to start with:
notion_read_database 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_database call is checked against it from then on.
Questions about notion_read_database
Reads the cached rows of a Notion database with their properties mapped through the schema. Accepts the database id or name (partial match). Only locally-cached rows are returned. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
notion_read_database accepts 2 parameters: limit, database. Required: database. 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_database: 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_database 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_database 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_database. 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_database 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