update_block · Notion MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_block does on Notion MCP Server

AI agents use update_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.

WHY IT NEEDS A POLICY

Why update_block needs a policy

This tool modifies existing Notion blocks (e.g., text content, formatting, properties) reversibly. It does not delete data (that would be delete_block), execute arbitrary code, or cause financial impact. The medium severity reflects that block updates could affect shared workspace content, but the change is reversible and localized to a single block unless the AI agent systematically corrupts many blocks.

From the tool's definition Tool name 'update_block' and description 'Update a Notion block' indicate modification of existing data. The server exposes 'the full Notion API' for managing 'blocks' with an integration token, confirming write capability without deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_block Rate-limited

update_block stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_block": {
      "limits": [
        {
          "counter": "update_block_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Notion MCP Server, so you can run agents against it safely.

FAQ

Questions about update_block

What does the update_block tool do? +

Update a 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.

How do I enforce a policy on update_block? +

Register the Notion MCP Server MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_block? +

update_block is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_block? +

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

How do I block update_block completely? +

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

What MCP server provides update_block? +

update_block 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.