update_database · Notion MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_database does on Notion MCP Server

AI agents use update_database 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_database needs a policy

Updating database schema (adding, modifying, or deleting properties/columns) is a Write operation as it reversibly alters data structure. While schema changes could have broad impact on dependent queries and records, they are not irreversible deletions (which would be Destructive). The operation is reversible—properties and columns can be re-added or modified again.

From the tool's definition Tool description explicitly states it 'Updates the database itself' and 'Can change database title or update schema (add/modify/delete properties/columns)'. This modifies database structure and metadata.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_database Rate-limited

update_database 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_database": {
      "limits": [
        {
          "counter": "update_database_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_database

What does the update_database tool do? +

Updates the database itself (not individual records). Can change database title or update schema (add/modify/delete properties/columns). Note: To update individual records, use update_page instead. 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_database? +

Register the Notion MCP Server MCP server in PolicyLayer and add a rule for update_database: 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_database? +

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

Can I rate-limit update_database? +

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

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

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