update-notion-block
AI agents use update-notion-block to create or update resources in Notion MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Notion MCP Server environment.
Based on naming convention and context from sibling tools, 'update-notion-block' modifies existing Notion block content. This is reversible (data can be updated again or reverted), placing it in the Write category rather than Destructive. Severity is medium because uncontrolled updates to Notion blocks could corrupt documentation, but the impact is limited to a single workspace and is recoverable.
From the tool's definition Tool name is 'update-notion-block' with no description provided. Sibling tools include 'delete-notion-block' (Destructive), 'create-notion-page' (Write), and 'update-notion-page' (Write).
Attacks that exploit this kind of access
update-notion-block. It is categorised as a Write tool in the Notion MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Notion MCP Server MCP server in PolicyLayer and add a rule for update-notion-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 Notion MCP Server. Nothing to install.
update-notion-block is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update-notion-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 update-notion-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.
update-notion-block is provided by the Notion MCP Server MCP server (joonhuang/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 →