upload_drive_file
Upload a file into Drive at a full path including filename. Provide exactly one source: ${UPLOAD_SOURCE_SEMANTICS} By default createParents=true creates missing parent folders and reports them.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/upload-drive-file.md
What upload_drive_file does on Huly
AI agents use upload_drive_file 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 is rated Medium
This tool creates or modifies files in a drive system, fitting the Write category (reversible data creation/modification). Severity is medium because uploading files could introduce malware, consume storage, or create unintended documents, but the effect is reversible via deletion. Confidence is high given the explicit 'upload' language and creation semantics.
From the tool's definition Tool name 'upload_drive_file' and description 'Upload a file into Drive at a full path' indicate file creation/modification. The parameter 'createParents=true' shows it can create parent folders, all reversible operations.
Attacks that exploit this kind of access
The rule that runs upload_drive_file 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, this is the rule to start with:
upload_drive_file 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 call is checked against it from then on.
Questions about upload_drive_file
Upload a file into Drive at a full path including filename. Provide exactly one source: ${UPLOAD_SOURCE_SEMANTICS} By default createParents=true creates missing parent folders and reports them. 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: 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 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 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. 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 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