notion_append_block_children
AI agents use notion_append_block_children to create or update resources in Integrations MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Integrations MCP environment.
The name 'append_block_children' strongly implies writing new child blocks to an existing Notion page or block, which is a reversible write operation. The description is empty, so confidence is reduced, but the naming convention is clear. Severity is medium as it modifies Notion content but does not delete or overwrite existing data.
From the tool's definition Tool name: notion_append_block_children — 'append' indicates adding new content to an existing Notion block/page.
Attacks that exploit this kind of access
notion_append_block_children. It is categorised as a Write tool in the Integrations MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Integrations 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 Integrations MCP. 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 Integrations MCP server (shriram-vasudevan/integrations-mcp). 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 →