Group matching rows in a configured source by one property and return counts per value.
AI agents call notion_source_group_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 groups and counts rows from a Notion database by a property value, then returns statistics. It retrieves data without side effects, modifying nothing. The sibling tools reveal the server's capabilities: write operations are handled by separate tools like notion_db_add_property and notion_db_remove_property. The notion_source_group_count function is purely analytical (Read category).
From the tool's definition Tool performs grouping and counting of matching rows with no modification capability—'return counts per value' indicates aggregation/retrieval only. Name and description contain no language suggesting create, update, delete, or execute operations.
Attacks that exploit this kind of access
Group matching rows in a configured source by one property and return counts per value. 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_source_group_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_source_group_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_source_group_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_source_group_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_source_group_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 →