AI agents use bulk_add_rows to create or update resources in Notion — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Notion environment.
This tool creates multiple database records in Notion, which is a reversible modification. It does not delete, execute arbitrary code, move money, or retrieve data. Severity is medium because bulk operations can affect many records, but the action is reversible and limited in scope to database row creation without executing code or destructive actions.
From the tool's definition Tool description states 'Add multiple rows to a database at once' — a write operation that creates data in Notion. The verb 'add' and 'rows' confirm data creation rather than retrieval or destruction.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Add multiple rows to a database at once. It is categorised as a Write tool in the Notion MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Notion MCP server in PolicyLayer and add a rule for bulk_add_rows: 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. Nothing to install.
bulk_add_rows 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 bulk_add_rows 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 bulk_add_rows. 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.
bulk_add_rows is provided by the Notion MCP server (kuldeepjha5176/notion-mcp-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 →