Append child blocks to a parent. Max 100 blocks, 2 nesting levels.
AI agents use notion_append_block_children 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.
This tool adds new content blocks to an existing Notion page or block. It creates/modifies data but is reversible (blocks can be deleted). The max 100 blocks limit and nesting constraints confirm it's a content write operation with moderate blast radius if misused to flood pages with unwanted content.
From the tool's definition Append child blocks to a parent
Attacks that exploit this kind of access
Append child blocks to a parent. Max 100 blocks, 2 nesting levels. 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_append_block_children: 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_append_block_children 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_append_block_children 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_append_block_children. 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_append_block_children 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 →