convertPdfToGoogleDoc
Convert an existing PDF in Drive into an editable Google Doc
This record as markdown: /tools/ark7-google-drive-mcp/convertpdftogoogledoc.md
What convertPdfToGoogleDoc does on Google Drive
AI agents use convertPdfToGoogleDoc 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 |
|---|---|---|---|
fileId | string | Yes | PDF file ID in Google Drive |
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 |
newName | string | — | Optional name for converted Doc |
parentFolderId | string | — | Optional destination folder ID |
Parameters from the server's own tool schema.
Why convertPdfToGoogleDoc is rated Medium
Converting a PDF to a Google Doc creates a new file resource and modifies the state of the Drive ecosystem (adding a new document). This is clearly a Write operation—it creates/modifies data reversibly and does not delete, execute arbitrary code, or move funds.
From the tool's definition Tool description states 'Convert an existing PDF in Drive into an editable Google Doc', which creates a new document by transforming an existing file. This is a reversible modification/creation of data within Google Drive.
Attacks that exploit this kind of access
The rule that runs convertPdfToGoogleDoc 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 convertPdfToGoogleDoc, this is the rule to start with:
convertPdfToGoogleDoc 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 convertPdfToGoogleDoc call is checked against it from then on.
Questions about convertPdfToGoogleDoc
Convert an existing PDF in Drive into an editable Google Doc. 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.
convertPdfToGoogleDoc accepts 4 parameters: fileId, account, newName, parentFolderId. Required: fileId. 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 convertPdfToGoogleDoc: 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.
convertPdfToGoogleDoc 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 convertPdfToGoogleDoc 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 convertPdfToGoogleDoc. 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.
convertPdfToGoogleDoc 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