query_data_source · Notion MCP Server MCP: Risk & Policy

WHAT IT DOES

What query_data_source does on Notion MCP Server

AI agents invoke query_data_source 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.

WHY IT NEEDS A POLICY

Why query_data_source needs a policy

Querying a data source is an Execute-category action because it runs a query operation whose effects and data retrieved depend on the arguments provided. While a simple read-only query might be categorized as Read, 'query_data_source' in the context of a full Notion API server (which includes create/delete sibling tools) likely executes a structured query against a data source, potentially with filters, sorts, and…

From the tool's definition "Query a data source" — the tool is named 'query_data_source' and described as querying a data source, which implies executing a query operation against a data source.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

query_data_source Rate-limited

query_data_source 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_data_source": {
      "limits": [
        {
          "counter": "query_data_source_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Notion MCP Server, so you can run agents against it safely.

FAQ

Questions about query_data_source

What does the query_data_source tool do? +

Query a data source. 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.

How do I enforce a policy on query_data_source? +

Register the Notion MCP Server MCP server in PolicyLayer and add a rule for query_data_source: 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.

What risk level is query_data_source? +

query_data_source is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit query_data_source? +

Yes. Add a rate_limit block to the query_data_source 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_data_source completely? +

Set action: deny in the PolicyLayer policy for query_data_source. 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_data_source? +

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