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.
This tool creates or modifies data reversibly. Updating a database schema or properties is a write operation that can typically be undone or rolled back. It does not irreversibly delete data (which would be Destructive), does not execute arbitrary code (Execute), and does not move money (Financial).
From the tool's definition Tool name is 'update_database' and description states 'Update a database'. The sibling tools include destructive operations ('delete_block') and read operations ('read_page', 'query_database'), but this tool's name and description explicitly indicate…
Documented attack patterns abuse exactly the kind of access update_database gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Notion MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_database:
{
"version": "1",
"default": "deny",
"tools": {
"update_database": {
"limits": [
{
"counter": "update_database_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Update a database. 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_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.
update_database 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_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.
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.
update_database is provided by the Notion MCP Server MCP server (v-3/notion-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 Notion MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 Notion MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.