Create or update Notion pages from Markdown with YAML frontmatter. Mode (default "auto"): if frontmatter has "id" → update, otherwise → create. Batch mode Separate multiple pages with a line containing only "===" to create/update them in one call. Frontmatter fields | Field | Create | Update | De...
Part of the Better Mcp Notion server.
Free to start. No card required.
AI agents use write to create or modify resources in Better Mcp Notion. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call write repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Better Mcp Notion.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"write": {
"limits": [
{
"counter": "write_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Better Mcp Notion policy for all 9 tools.
These attack patterns abuse exactly the kind of access write gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Create or update Notion pages from Markdown with YAML frontmatter. Mode (default "auto"): if frontmatter has "id" → update, otherwise → create. Batch mode Separate multiple pages with a line containing only "===" to create/update them in one call. Frontmatter fields | Field | Create | Update | Description | |-------|--------|--------|-------------| | id | - | required | Page ID to update | | title | recommended | optional | Page title | | parent | required* | ignored | Parent page name or ID | | database | required* | ignored | Database name or ID (*either parent or database) | | icon | optional | optional | Emoji (e.g. 📋) or image URL | | cover | optional | optional | Cover image URL | | properties | optional | optional | DB properties (see below) | Properties are auto-matched to the database schema. Use the exact property name as key. Read-only fields from read output (url, created, last_edited, formula, etc.) are safely ignored. Examples Create a page under a parent page: --- title: Meeting Notes parent: "Project Alpha" icon: "📝" --- Agenda - Review progress Create a database entry: --- title: Fix login bug database: "Task Board" properties: Status: In Progress Tags: - backend - urgent Due Date: "2026-03-01" --- Description Login fails when password contains special chars. Update an existing page (edit output from read): --- id: abc123-def456 title: Updated Title properties: Status: Done --- New content Body replaces all existing blocks. Append to an existing page (add content without rewriting): Use position: "append" to add content to the end, or "prepend" to add to the beginning. Only the new content needs to be provided — existing content is preserved. --- id: abc123-def456 --- New section added at the end Batch create (multiple pages in one call): --- title: Task 1 database: "Task Board" properties: Status: Todo --- Task 1 details === --- title: Task 2 database: "Task Board" properties: Status: Todo --- Task 2 details. It is categorised as a Write tool in the Better Mcp Notion MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Better Mcp Notion MCP server in PolicyLayer and add a rule for write: 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 Better Mcp Notion. Nothing to install.
write 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 write 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 write. 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.
write is provided by the Better Mcp Notion MCP server (better-mcp-notion). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 Better Mcp Notion tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.