AI agents invoke query-database to trigger actions in Notion MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The name 'query-database' suggests querying a Notion database, which is typically a Read operation. However, with an empty description, it's unclear whether it executes arbitrary queries or just retrieves data. Given the sibling tools context (Notion SDK interactions) and the name, it most likely performs a filtered/sorted read against a Notion database. Lowering confidence due to missing description.
From the tool's definition Tool name: 'query-database'; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access query-database gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Notion MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for query-database:
{
"version": "1",
"default": "deny",
"tools": {
"query-database": {
"limits": [
{
"counter": "query-database_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}query-database stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
query-database. It is categorised as a Execute tool in the Notion MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Notion 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 MCP Server. Nothing to install.
query-database is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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 MCP Server MCP server (ramidecodes/mcp-server-notion). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Notion 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 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.