upload_drive_file_version
Upload a new version for an existing Drive file resolved by file id or file path. Provide exactly one source: ${UPLOAD_SOURCE_SEMANTICS} This increments the file version counter and makes the uploaded version current.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/upload-drive-file-version.md
What upload_drive_file_version does on Huly
AI agents use upload_drive_file_version to create or update resources in Huly, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Huly environment.
Why upload_drive_file_version is rated Medium
This tool creates a new version of a file and sets it as current, which is a reversible Write operation. It modifies file metadata and content but does not delete the original version (versions are typically retained in document management systems).
From the tool's definition 'Upload a new version for an existing Drive file' and 'increments the file version counter and makes the uploaded version current' indicate the tool modifies (updates) existing file data.
Attacks that exploit this kind of access
The rule that runs upload_drive_file_version safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For upload_drive_file_version, this is the rule to start with:
upload_drive_file_version 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 Huly, apply this rule, and every upload_drive_file_version call is checked against it from then on.
Questions about upload_drive_file_version
Upload a new version for an existing Drive file resolved by file id or file path. Provide exactly one source: ${UPLOAD_SOURCE_SEMANTICS} This increments the file version counter and makes the uploaded version current. It is categorised as a Write tool in the Huly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Huly MCP server in PolicyLayer and add a rule for upload_drive_file_version: 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 Huly. Nothing to install.
upload_drive_file_version 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 upload_drive_file_version 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 upload_drive_file_version. 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.
upload_drive_file_version is provided by the Huly MCP server (@firfi/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Huly, and thousands of servers like it.
This server
Across the catalogue