Low Risk

notion_get_page_content

Get the content blocks of a Notion page

How to control notion_get_page_content ↓

AI agents call notion_get_page_content to retrieve information from Sage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves and queries data from a Notion page without creating, modifying, or deleting any content. It is a straightforward read operation. Severity is low because the worst-case misuse would be unauthorized access to page content, but the impact is limited to information disclosure within the authenticated user's Notion workspace.

From the tool's definition Tool name 'notion_get_page_content' and description 'Get the content blocks of a Notion page' indicate a retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access notion_get_page_content gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for notion_get_page_content:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "notion_get_page_content": {}
  }
}

notion_get_page_content is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Sage MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the notion_get_page_content tool do? +

Get the content blocks of a Notion page. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on notion_get_page_content? +

Register the Sage MCP server in PolicyLayer and add a rule for notion_get_page_content: 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 Sage MCP. Nothing to install.

What risk level is notion_get_page_content? +

notion_get_page_content is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit notion_get_page_content? +

Yes. Add a rate_limit block to the notion_get_page_content 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.

How do I block notion_get_page_content completely? +

Set action: deny in the PolicyLayer policy for notion_get_page_content. 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.

What MCP server provides notion_get_page_content? +

notion_get_page_content is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sage MCP tool call.

Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.