Query a Notion database
AI agents call query_database to retrieve information from Notion Direct MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Querying a database is a retrieval operation with no side effects. It retrieves or returns data matching criteria but does not create, modify, delete, or execute code. The server description confirms this tool supports 'database queries' as a core operation alongside separate write/update functions (create_page, update_page, append_blocks). The blast radius of misuse is limited to potential information disclosure.
From the tool's definition Tool name 'query_database' and description 'Query a Notion database' indicate a read-only operation that retrieves data from a Notion database without modifying or deleting content.
Attacks that exploit this kind of access
Query a Notion database. It is categorised as a Read tool in the Notion Direct MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Notion Direct MCP Server MCP server in PolicyLayer and add a rule for query_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 Notion Direct MCP Server. Nothing to install.
query_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 query_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 query_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.
query_database is provided by the Notion Direct MCP Server MCP server (wayy-research/notion-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →