uploadPdfWithSplit
Upload PDF and optionally split into chunked parts (metadata split plan for now)
This record as markdown: /tools/ark7-google-drive-mcp/uploadpdfwithsplit.md
What uploadPdfWithSplit does on Google Drive
AI agents use uploadPdfWithSplit 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 |
|---|---|---|---|
split | boolean | — | Enable split mode |
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 |
localPath | string | Yes | Absolute path to local PDF |
namePrefix | string | — | Optional output name prefix |
parentFolderId | string | — | Optional destination folder ID |
maxPagesPerChunk | number | — | Target max pages per chunk (advisory metadata) |
Parameters from the server's own tool schema.
Why uploadPdfWithSplit is rated Medium
This tool creates new data (PDF file upload) and optionally modifies it through chunking/splitting. File uploads are write operations with medium severity because they consume storage resources and can overwrite existing files if naming conflicts occur, but the operation is reversible (files can be deleted). The blast radius is contained to the user's Drive storage unless permissions allow broader access.
From the tool's definition Tool name 'uploadPdf' and description 'Upload PDF' indicate file creation/modification. The 'WithSplit' suffix suggests processing that transforms the uploaded file into chunked parts, which is a reversible modification rather than deletion.
Attacks that exploit this kind of access
The rule that runs uploadPdfWithSplit 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 uploadPdfWithSplit, this is the rule to start with:
uploadPdfWithSplit 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 uploadPdfWithSplit call is checked against it from then on.
Questions about uploadPdfWithSplit
Upload PDF and optionally split into chunked parts (metadata split plan for now). 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.
uploadPdfWithSplit accepts 6 parameters: split, account, localPath, namePrefix, parentFolderId, maxPagesPerChunk. Required: localPath. 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 uploadPdfWithSplit: 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.
uploadPdfWithSplit 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 uploadPdfWithSplit 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 uploadPdfWithSplit. 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.
uploadPdfWithSplit 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