Count rows in a configured source by one exact property match, using schema-aware filter construction.
AI agents call notion_source_count_by_property 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 retrieves aggregate count information from a Notion database based on property filters. It performs a read-only query operation with no side effects—no data is created, modified, deleted, or executed.
From the tool's definition Tool name contains 'count' and description states it 'Count rows' with 'exact property match' and 'filter construction'. No modification, deletion, or execution keywords present.
Attacks that exploit this kind of access
Count rows in a configured source by one exact property match, using schema-aware filter construction. 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_count_by_property: 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_count_by_property 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_count_by_property 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_count_by_property. 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_count_by_property 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 →