Update page or database item properties
AI agents use notion_update_page_properties 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.
The tool creates or modifies data reversibly by updating properties of pages or database items. While it changes state, it does not irreversibly delete data (which would be Destructive) nor execute arbitrary code (which would be Execute).
From the tool's definition Tool name includes 'update' and description states 'Update page or database item properties' — this modifies existing data in Notion workspaces.
Attacks that exploit this kind of access
Update page or database item properties. 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.
Register the MCP Notion Server (@suncreation) MCP server in PolicyLayer and add a rule for notion_update_page_properties: 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.
notion_update_page_properties 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 notion_update_page_properties 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 notion_update_page_properties. 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.
notion_update_page_properties 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →