notion_source_update_schema · Notion DB MCP Helper MCP

WHAT IT DOES

What notion_source_update_schema does on Notion DB MCP Helper

AI agents use notion_source_update_schema to create or update resources in Notion DB MCP Helper — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Notion DB MCP Helper environment.

WHY IT NEEDS A POLICY

Why notion_source_update_schema needs a policy

This tool modifies schema configuration by altering properties (add, rename, update, remove). While 'remove' might suggest destructiveness, the context is schema property management rather than data deletion—properties are redefined rather than irreversibly purged.

From the tool's definition Tool description states it can 'add, rename, update, or remove properties' to a source schema. The verb 'Patch' and the ability to modify properties are explicit indicators of data modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

notion_source_update_schema Rate-limited

notion_source_update_schema 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": {
    "notion_source_update_schema": {
      "limits": [
        {
          "counter": "notion_source_update_schema_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 DB MCP Helper, so you can run agents against it safely.

FAQ

Questions about notion_source_update_schema

What does the notion_source_update_schema tool do? +

Patch a configured source schema by passing a raw Notion data source properties object. Can add, rename, update, or remove properties. It is categorised as a Write tool in the Notion DB MCP Helper MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on notion_source_update_schema? +

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

What risk level is notion_source_update_schema? +

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

Can I rate-limit notion_source_update_schema? +

Yes. Add a rate_limit block to the notion_source_update_schema 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_source_update_schema completely? +

Set action: deny in the PolicyLayer policy for notion_source_update_schema. 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_source_update_schema? +

notion_source_update_schema is provided by the Notion DB MCP Helper MCP server (trisetiohidayat/notion-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.