Add a row to a table block. Cells count must match table_width.
AI agents use notion_table_add_row 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 creates or modifies data (adds a new row) in a reversible manner. It does not delete data (not Destructive), execute arbitrary code (not Execute), handle financial transactions (not Financial), or merely read data (not Read).
From the tool's definition Tool name 'notion_table_add_row' and description 'Add a row to a table block' indicate creation of new data within an existing table structure.
Attacks that exploit this kind of access
Add a row to a table block. Cells count must match table_width. 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_table_add_row: 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_table_add_row 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_table_add_row 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_table_add_row. 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_table_add_row 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 →