Appends rows to the end of a sheet (after the last row with data). Data should be JSON 2D array.
AI agents use add_rows to create or update resources in Google Sheets MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Sheets MCP Server environment.
add_rows creates new data entries in a spreadsheet in a reversible manner. It does not execute arbitrary code, delete data, move money, or retrieve data without side effects. While it modifies state, the operation can be undone (rows can be deleted), placing it firmly in the Write category rather than Execute or Destructive.
From the tool's definition Tool description states 'Appends rows to the end of a sheet', which is a create/add operation that modifies data reversibly.
Attacks that exploit this kind of access
Appends rows to the end of a sheet (after the last row with data). Data should be JSON 2D array. It is categorised as a Write tool in the Google Sheets MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Sheets MCP Server MCP server in PolicyLayer and add a rule for 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 Google Sheets MCP Server. Nothing to install.
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 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 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.
add_rows is provided by the Google Sheets MCP Server MCP server (santiagopereda/mcp_googlesheets). 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 →