Add one or more new rows to the next empty row(s).
AI agents use add_row to create or update resources in Google Connections — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Connections environment.
This tool creates new data rows in a spreadsheet, which is a reversible write operation. It does not delete data (not Destructive), execute arbitrary code (not Execute), involve financial transactions (not Financial), or merely read data (not Read). The blast radius is medium because unintended row additions could clutter data or disrupt spreadsheet structure, but changes can be undone.
From the tool's definition Tool description: 'Add one or more new rows to the next empty row(s).' The verb 'Add' and the action of inserting new rows into a spreadsheet indicates data creation/modification. Server context confirms this operates on Google Sheets (CRUD operations).
Attacks that exploit this kind of access
Add one or more new rows to the next empty row(s). It is categorised as a Write tool in the Google Connections MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Connections MCP server in PolicyLayer and add a rule for 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 Google Connections. Nothing to install.
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 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 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.
add_row is provided by the Google Connections MCP server (michaelzrork/google-connections-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 →