notion_update_database

WHAT IT DOES

What notion_update_database does on MCP Notion Server (@suncreation)

AI agents use notion_update_database to create or update resources in MCP Notion Server (@suncreation) — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Notion Server (@suncreation) environment.

WHY IT NEEDS A POLICY

Why notion_update_database needs a policy

Updating a database is a reversible modification operation that changes database configuration, properties, or structure without permanently deleting data. While the blast radius is significant (affects all dependent pages/queries in a Notion workspace), the action is reversible through undo or restoring previous versions. This places it in the Write category rather than Destructive.

From the tool's definition Tool name contains 'update' and description explicitly states 'Update a database'. The MCP server documentation indicates it supports 'database management', and this tool modifies existing database structures or properties.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

notion_update_database Rate-limited

notion_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": {
    "notion_update_database": {
      "limits": [
        {
          "counter": "notion_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 MCP Notion Server (@suncreation), so you can run agents against it safely.

FAQ

Questions about notion_update_database

What does the notion_update_database tool do? +

Update a database. It is categorised as a Write tool in the MCP Notion Server (@suncreation) 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_update_database? +

Register the MCP Notion Server (@suncreation) MCP server in PolicyLayer and add a rule for notion_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 MCP Notion Server (@suncreation). Nothing to install.

What risk level is notion_update_database? +

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

Can I rate-limit notion_update_database? +

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

Set action: deny in the PolicyLayer policy for notion_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 notion_update_database? +

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