Retrieve a block
AI agents call notion_retrieve_block to retrieve information from MCP Notion Server (@suncreation) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves block information from Notion without creating, modifying, or deleting data. It is a straightforward read operation with minimal security risk—the primary concern would be unauthorized access to sensitive information within blocks, but the tool itself performs no destructive or harmful actions by default.
From the tool's definition Tool name 'notion_retrieve_block' with description 'Retrieve a block' indicates data retrieval with no modification. The verb 'retrieve' and absence of write/delete/create operations confirm read-only behavior.
Attacks that exploit this kind of access
Retrieve a block. It is categorised as a Read tool in the MCP Notion Server (@suncreation) MCP Server, which means it retrieves data without modifying state.
Register the MCP Notion Server (@suncreation) MCP server in PolicyLayer and add a rule for notion_retrieve_block: 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 MCP Notion Server (@suncreation). Nothing to install.
notion_retrieve_block 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_block 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_block. 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_block is provided by the MCP Notion Server (@suncreation) MCP server (suncreation/mcp-notion-server). 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 →