Merge a range of cells into one.
AI agents use merge_cells 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.
Merging cells modifies the structure and formatting of a spreadsheet but does not delete data, create irreversible changes, or execute arbitrary code. The operation is reversible (cells can be unmerged), making it a Write-category tool. Severity is low because the blast radius of misuse is limited to formatting changes within a single sheet, with no data loss or financial impact.
From the tool's definition Tool name 'merge_cells' and description 'Merge a range of cells into one' indicate a reversible modification operation on Google Sheets cells.
Attacks that exploit this kind of access
Merge a range of cells into one. 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 merge_cells: 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.
merge_cells 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 merge_cells 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 merge_cells. 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.
merge_cells 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 →