notion_list_databases
Lists Notion databases cached on this Mac with their schema (column names and types). Use notion_read_database to get the rows.
This record as markdown: /tools/com-local-mcp-local-mcp/notion-list-databases.md
What notion_list_databases does on Local
AI agents call notion_list_databases 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.
Why notion_list_databases is rated Low
This tool retrieves and queries cached Notion database metadata (names and schema). It performs no side effects, creates no data, executes no code, and causes no destructive changes. The description explicitly distinguishes this from notion_read_database (which reads rows), emphasizing its limited scope to schema introspection.
From the tool's definition Tool description states it 'Lists Notion databases cached on this Mac with their schema (column names and types).' The verb 'lists' and the focus on retrieving schema information indicates a read-only operation with no data modification.
Attacks that exploit this kind of access
The rule that runs notion_list_databases 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_databases, this is the rule to start with:
notion_list_databases 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_databases call is checked against it from then on.
Questions about notion_list_databases
Lists Notion databases cached on this Mac with their schema (column names and types). Use notion_read_database to get the rows. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
Register the Local MCP server in PolicyLayer and add a rule for notion_list_databases: 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_databases 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_databases 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_databases. 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_databases 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