Clear cell contents in a range without deleting rows/columns.
AI agents call clear_range to permanently remove resources in Google Connections — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing cell contents removes data without the ability to undo through the API. While it does not delete rows or columns, the data within the specified range is permanently erased. This qualifies as Destructive since the content loss is irreversible via the tool itself. The blast radius is high because a broad range could wipe significant spreadsheet data.
From the tool's definition 'Clear cell contents in a range' — removes data from cells irreversibly
Attacks that exploit this kind of access
Clear cell contents in a range without deleting rows/columns. It is categorised as a Destructive tool in the Google Connections MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Connections MCP server in PolicyLayer and add a rule for clear_range: 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.
clear_range is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_range 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 clear_range. 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.
clear_range 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 →