insertSmartChip
Insert a person smart chip (mention) at a document index. Only person chips are supported by the Docs API; date and file chips are read-only.
This record as markdown: /tools/ark7-google-drive-mcp/insertsmartchip.md
What insertSmartChip does on Google Drive
AI agents use insertSmartChip to create or update resources in Google Drive, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Drive environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
index | number | Yes | Insertion index (1-based) |
tabId | string | — | Optional. Tab ID to insert into (from listDocumentTabs). If omitted, inserts into the first/default tab. |
account | string | — | Alias of the Google account to target. Optional — defaults to the session/global default account, or the sole authenticated account. Run manage_accounts list to |
chipType | string | Yes | Smart chip type (only 'person' is supported) |
documentId | string | Yes | Document ID |
personEmail | string | Yes | Email address for the person mention |
ifRevisionId | string | — | Optional optimistic lock: a revisionId from readGoogleDoc, getGoogleDocContent, getGoogleDocContentPaginated, or getDocumentInfo. The write fails cleanly if the |
Parameters from the server's own tool schema.
Why insertSmartChip is rated Medium
This tool creates and inserts new data (a person mention/smart chip) into a Google Docs document, which is reversible and represents a Write action. Severity is medium because unintended insertions could spam documents with unwanted mentions, but the impact is limited to document content modification without data loss or external effects.
From the tool's definition Tool description explicitly states 'Insert a person smart chip (mention) at a document index', using the verb 'Insert' which creates new content in a document. The description confirms this modifies document state by adding a mention reference.
Attacks that exploit this kind of access
The rule that runs insertSmartChip safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Drive, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For insertSmartChip, this is the rule to start with:
insertSmartChip stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Google Drive, apply this rule, and every insertSmartChip call is checked against it from then on.
Questions about insertSmartChip
Insert a person smart chip (mention) at a document index. Only person chips are supported by the Docs API; date and file chips are read-only. It is categorised as a Write tool in the Google Drive MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
insertSmartChip accepts 7 parameters: index, tabId, account, chipType, documentId, personEmail, ifRevisionId. Required: index, chipType, documentId, personEmail. The full parameter table on this page comes from the server's own tool schema.
Register the Google Drive MCP server in PolicyLayer and add a rule for insertSmartChip: 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 Drive. Nothing to install.
insertSmartChip 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 insertSmartChip 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 insertSmartChip. 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.
insertSmartChip is provided by the Google Drive MCP server (@ark7/google-drive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Drive, and thousands of servers like it.
This server
Across the catalogue