Find and delete excessive empty lines/paragraphs from a Google Doc.
AI agents call delete_empty_lines 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.
The tool deletes content (empty lines/paragraphs) from a Google Doc. While it only targets whitespace/empty lines, this is still a destructive modification that removes existing document content and may not be easily reversible. Severity is medium because the content deleted is limited to empty lines rather than meaningful data, but the action is still irreversible without version history.
From the tool's definition 'delete excessive empty lines/paragraphs from a Google Doc' — permanently removes content from the document
Attacks that exploit this kind of access
Find and delete excessive empty lines/paragraphs from a Google Doc. 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 delete_empty_lines: 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.
delete_empty_lines 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 delete_empty_lines 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 delete_empty_lines. 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.
delete_empty_lines 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 →