AI agents use insert_rich_link to create or update resources in Google — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google environment.
This tool creates new content (a rich link/smart chip) within an existing Google Doc, which is a reversible modification. It does not execute arbitrary code, delete data, or move funds. The write category is appropriate. Severity is low because inserting a link has minimal blast radius—the worst case is insertion of unintended links that clutter the document, but this is easily reversible via undo or manual deletion.
From the tool's definition Tool description explicitly states 'Insert a rich link...into a Google Doc', indicating it creates/adds content to a document. The verb 'insert' and the context of modifying a Doc by adding a link confirms write-level functionality.
Attacks that exploit this kind of access
Insert a rich link (smart chip) to a Google file into a Google Doc. It is categorised as a Write tool in the Google MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google MCP server in PolicyLayer and add a rule for insert_rich_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. Nothing to install.
insert_rich_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_rich_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_rich_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_rich_link is provided by the Google MCP server (ztgluis/google-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 →