Add a hyperlink to existing text in a Google Doc.
AI agents use insert_link 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.
The tool modifies Google Doc content by inserting a hyperlink into existing text. This is a Create/Modify operation (Write category) rather than Read (no data retrieval), Execute (no code execution), Destructive (reversible change), or Financial (no money involved).
From the tool's definition Tool name 'insert_link' and description 'Add a hyperlink to existing text in a Google Doc' indicate modification of document content. This is a write operation that creates or modifies data reversibly without destructive effects.
Attacks that exploit this kind of access
Add a hyperlink to existing text in a Google Doc. 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 insert_link: 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.
insert_link 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 insert_link 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 insert_link. 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.
insert_link 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 →