Retrieve the bot user associated with the current token in Notion
AI agents call notion_retrieve_bot_user 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 fetches metadata about the authenticated bot user. It is a read-only operation that queries Notion's API to return information about the current token's associated bot user. No data is created, modified, deleted, or executed. The blast radius is minimal—only authenticated metadata about the integration itself is returned, which is necessary for normal operation of the MCP integration.
From the tool's definition Tool name contains 'retrieve' and description states 'Retrieve the bot user' — a straightforward query operation with no modification or side effects.
Attacks that exploit this kind of access
Retrieve the bot user associated with the current token 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_retrieve_bot_user: 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_retrieve_bot_user 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_retrieve_bot_user 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_retrieve_bot_user. 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_retrieve_bot_user is provided by the Notion MCP Server MCP server (tkc/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 →