Freeze rows and/or columns in a worksheet.
AI agents use freeze_rows_columns 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.
Freezing rows/columns is a write operation that modifies worksheet configuration reversibly. It does not delete, execute code, move money, or trigger external operations. The change is easily undoable by unfreezing, placing it in the Write category with low severity due to minimal blast radius—affects only formatting preferences, not data integrity or critical operations.
From the tool's definition Tool name 'freeze_rows_columns' and description 'Freeze rows and/or columns in a worksheet' indicates modification of worksheet formatting/state in Google Sheets. This is a reversible, non-destructive change to display settings.
Attacks that exploit this kind of access
Freeze rows and/or columns in a worksheet. 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 freeze_rows_columns: 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.
freeze_rows_columns 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 freeze_rows_columns 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 freeze_rows_columns. 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.
freeze_rows_columns 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 →