Count rows in a Notion data source that match an optional Notion API filter.
AI agents call notion_db_count to retrieve information from Notion DB MCP Helper without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation—counting rows matching criteria—with no side effects. It does not create, modify, delete, or execute external operations. The count operation is a retrieval query analogous to SELECT COUNT(*) in SQL, which is a classic Read category operation.
From the tool's definition Tool name 'notion_db_count' and description 'Count rows in a Notion data source that match an optional Notion API filter' indicates a query operation that retrieves aggregate data without modifying or deleting any rows.
Attacks that exploit this kind of access
Count rows in a Notion data source that match an optional Notion API filter. It is categorised as a Read tool in the Notion DB MCP Helper MCP Server, which means it retrieves data without modifying state.
Register the Notion DB MCP Helper MCP server in PolicyLayer and add a rule for notion_db_count: 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 DB MCP Helper. Nothing to install.
notion_db_count 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_db_count 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_db_count. 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_db_count is provided by the Notion DB MCP Helper MCP server (trisetiohidayat/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 →