Merge cells in a Google Sheet
AI agents use sheets_merge_cells to create or update resources in MCP Google Sheets Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Google Sheets Server environment.
Merging cells modifies the structure and formatting of a spreadsheet but does not delete data, execute code, or cause irreversible damage. It is a Write operation because it changes spreadsheet state reversibly. Severity is medium because misuse could corrupt spreadsheet layouts or make data harder to access, but the change is non-destructive and can be undone.
From the tool's definition Tool name 'sheets_merge_cells' and description 'Merge cells in a Google Sheet' indicate a modification operation that combines cell ranges. This is a reversible formatting change (cells can be unmerged).
Attacks that exploit this kind of access
Merge cells in a Google Sheet. It is categorised as a Write tool in the MCP Google Sheets Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Google Sheets Server MCP server in PolicyLayer and add a rule for sheets_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 MCP Google Sheets Server. Nothing to install.
sheets_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 sheets_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 sheets_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.
sheets_merge_cells is provided by the MCP Google Sheets Server MCP server (oregpt/agenticledger_mcp_sheetsonly). 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 →