AI agents call 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 comments, producing no side effects. It is analogous to sibling tools 'get-block-children' and 'get-database' which fetch data without modification. Confidence reduced slightly from 0.9 to 0.85 due to empty description, but the name and API pattern are clear. No data is created, modified, deleted, executed, or financial obligation incurred.
From the tool's definition Tool name 'list-comments' indicates a retrieval operation. The Notion MCP Server exposes read operations like 'get-page', 'get-database', 'get-block-children' which are clearly Read category.
Documented attack patterns abuse exactly the kind of access 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 list-comments:
{
"version": "1",
"default": "deny",
"tools": {
"list-comments": {}
}
}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-comments. 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 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.
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 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 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.
list-comments is provided by the Notion MCP Server MCP server (ramidecodes/mcp-server-notion). 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.
17 Notion MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.