Retrieve a data source by ID.
AI agents call retrieve_data_source 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.
The tool performs a read-only operation to retrieve/fetch a data source object by identifier. No data is created, modified, deleted, or executed. The absence of side effects and the use of 'retrieve' (a classic Read verb) places this firmly in the Read category with low severity.
From the tool's definition Tool name 'retrieve_data_source' and description 'Retrieve a data source by ID' indicate a query/fetch operation with no modification or deletion of data.
Attacks that exploit this kind of access
Retrieve a data source by ID. 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 retrieve_data_source: 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.
retrieve_data_source 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 retrieve_data_source 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 retrieve_data_source. 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.
retrieve_data_source is provided by the Notion MCP Server MCP server (lrgex/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 →