readSmartChips
Read smart chip-like elements (person mentions, rich links, date chips) from the default tab of a document
This record as markdown: /tools/ark7-google-drive-mcp/readsmartchips.md
What readSmartChips does on Google Drive
AI agents call readSmartChips to retrieve information from Google Drive without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
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 |
documentId | string | Yes | Document ID |
Parameters from the server's own tool schema.
Why readSmartChips is rated Low
This tool only retrieves existing data (person mentions, rich links, date chips) from a document without side effects. It performs a query-like operation on document content, matching the Read category definition. Low severity due to the limited blast radius—accessing embedded metadata poses minimal risk even if misused by an agent.
From the tool's definition Tool name contains 'read' and description states 'Read smart chip-like elements...from the default tab of a document'. The operation retrieves metadata about mentions, links, and dates without modifying or executing any operations.
Attacks that exploit this kind of access
The rule that runs readSmartChips 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 readSmartChips, this is the rule to start with:
readSmartChips is read-only, so it stays allowed. 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 readSmartChips call is checked against it from then on.
Questions about readSmartChips
Read smart chip-like elements (person mentions, rich links, date chips) from the default tab of a document. It is categorised as a Read tool in the Google Drive MCP Server, which means it retrieves data without modifying state.
readSmartChips accepts 2 parameters: account, documentId. Required: documentId. 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 readSmartChips: 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.
readSmartChips is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the readSmartChips 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 readSmartChips. 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.
readSmartChips 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