Low Risk

query_database

Query database with filters and sorting

How to control query_database ↓

What query_database does on Notion API MCP Server

AI agents call query_database to retrieve information from Notion API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why query_database needs a policy

This tool retrieves or searches data from a Notion database using filters and sorting parameters. It has no side effects—it returns results without altering the database state. This is a classic Read operation. The low severity reflects that misuse is limited to data access, which in a Notion context is relatively contained (assuming proper access controls upstream).

From the tool's definition Tool name 'query_database' and description 'Query database with filters and sorting' indicate retrieval operations. No language suggesting modification, deletion, or execution of arbitrary code.

Documented attack patterns abuse exactly the kind of access query_database gives an agent:

How to control query_database

PolicyLayer is an MCP gateway — it sits between your AI agents and Notion API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for query_database:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_database": {}
  }
}

query_database is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Notion API MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about query_database

What does the query_database tool do? +

Query database with filters and sorting. It is categorised as a Read tool in the Notion API MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_database? +

Register the Notion API 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 API MCP Server. Nothing to install.

What risk level is query_database? +

query_database is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit query_database? +

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.

How do I block query_database completely? +

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.

What MCP server provides query_database? +

query_database is provided by the Notion API MCP Server MCP server (pbohannon/notion-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Notion API MCP Server tool call.

Start from Notion API MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

17 Notion API MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.