New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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.

SERVERGoogle Drive SOURCE@ark7/google-drive-mcp
Medium RISK CLASS
Category Write
Parameters 74 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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.

Questions about insertSmartChip

What does the insertSmartChip tool do? +

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.

What parameters does insertSmartChip accept? +

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.

How do I enforce a policy on insertSmartChip? +

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.

What risk level is insertSmartChip? +

insertSmartChip is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit insertSmartChip? +

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.

How do I block insertSmartChip completely? +

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.

What MCP server provides insertSmartChip? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Google Drive's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.