AI agents call verify_connection to retrieve information from Notion API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool's purpose is to verify that the client can authenticate with the Notion API. It performs no data operations—it does not read, write, delete, or execute commands against Notion's database or content. It is a diagnostic/status check, which is the least intrusive type of operation. Classified as Read because it likely returns authentication status information without side effects.
From the tool's definition Tool is named 'verify_connection' and described as 'Verify authentication with Notion API'. This is a connection/authentication test that checks credentials without retrieving, modifying, deleting, or executing operations on data.
Documented attack patterns abuse exactly the kind of access verify_connection gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Notion API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for verify_connection:
{
"version": "1",
"default": "deny",
"tools": {
"verify_connection": {}
}
}verify_connection 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.
Verify authentication with Notion API. It is categorised as a Read tool in the Notion API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Notion API MCP Server MCP server in PolicyLayer and add a rule for verify_connection: 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 API MCP Server. Nothing to install.
verify_connection 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 verify_connection 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 verify_connection. 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.
verify_connection is provided by the Notion API MCP Server MCP server (pbohannon/notion-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Notion API 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 API MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.