AI agents call notion_list_comments to retrieve information from Notion MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries existing comment data from Notion blocks without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal security risk—exposure would only allow unauthorized viewing of comments, not their modification or deletion.
From the tool's definition Tool name 'notion_list_comments' and description 'List all comments for a block in Notion' indicate a retrieval operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access notion_list_comments 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 notion_list_comments:
{
"version": "1",
"default": "deny",
"tools": {
"notion_list_comments": {}
}
}notion_list_comments is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all comments for a block in Notion. It is categorised as a Read tool in the Notion MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Notion MCP Server MCP server in PolicyLayer and add a rule for notion_list_comments: 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.
notion_list_comments 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_list_comments 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_list_comments. 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_list_comments is provided by the Notion MCP Server MCP server (orbit-logistics/notion-mcp-server). 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.
21 Notion MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.