New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

agency-hosting_generateUploadURLV1

Generate a file browser upload URL with authentication credentials for uploading files to an Agency Plan website's file storage. Returns url, auth_key and rest_auth_key. Use these to upload a file to the website's file storage via the TUS resumable upload protocol (TUS 1.0.0). Send X-Auth: {auth_...

SERVERHostinger Api SOURCEhostinger-api-mcp
Medium RISK CLASS
Category Write
Parameters 11 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-generateuploadurlv1.md

What agency-hosting_generateUploadURLV1 does on Hostinger Api

AI agents use agency-hosting_generateUploadURLV1 to create or update resources in Hostinger Api, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger Api environment.

ParameterTypeRequiredDescription
website_uid string Yes Agency Plan website UID

Parameters from the server's own tool schema.

Why agency-hosting_generateUploadURLV1 is rated Medium

Creates/modifies website files reversibly via authenticated upload protocol; high blast radius if AI uploads malicious content.

From the tool's definition Generate upload URL with authentication; upload files to website storage

Risk signalsBulk/mass operation — affects multiple targets

Questions about agency-hosting_generateUploadURLV1

What does the agency-hosting_generateUploadURLV1 tool do? +

Generate a file browser upload URL with authentication credentials for uploading files to an Agency Plan website's file storage. Returns url, auth_key and rest_auth_key. Use these to upload a file to the website's file storage via the TUS resumable upload protocol (TUS 1.0.0). Send X-Auth: {auth_key} and X-Auth-Rest: {rest_auth_key} headers on every request below. 1. Create the upload: POST to {url}/{relative_file_path}?override=true with headers upload-length: {file size in bytes} and upload-offset: 0. Expect 201 Created. 2. Upload the file: send the file bytes to the same location (any TUS 1.0.0 client, or PATCH requests with an upload-offset header tracking progress) until complete. relative_file_path is the destination path inside the website's file storage, e.g. app.zip. Instead of a TUS client, plain curl also works: FILE=app.zip SIZE=$(stat -f%z "$FILE") # stat -c%s on Linux curl -i -X POST "{url}/${FILE}?override=true" \ -H "X-Auth: {auth_key}" \ -H "X-Auth-Rest: {rest_auth_key}" \ -H "Tus-Resumable: 1.0.0" \ -H "Upload-Length: ${SIZE}" \ -H "Upload-Offset: 0" -> 201 Created curl -i -X PATCH "{url}/${FILE}?override=true" \ -H "X-Auth: {auth_key}" \ -H "X-Auth-Rest: {rest_auth_key}" \ -H "Tus-Resumable: 1.0.0" \ -H "Content-Type: application/offset+octet-stream" \ -H "Upload-Offset: 0" \ --data-binary "@${FILE}" -> 204 No Content, Upload-Offset response header equals SIZE when done. It is categorised as a Write tool in the Hostinger Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does agency-hosting_generateUploadURLV1 accept? +

agency-hosting_generateUploadURLV1 accepts 1 parameter: website_uid. Required: website_uid. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on agency-hosting_generateUploadURLV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for agency-hosting_generateUploadURLV1: 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 Hostinger Api. Nothing to install.

What risk level is agency-hosting_generateUploadURLV1? +

agency-hosting_generateUploadURLV1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit agency-hosting_generateUploadURLV1? +

Yes. Add a rate_limit block to the agency-hosting_generateUploadURLV1 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.

How do I block agency-hosting_generateUploadURLV1 completely? +

Set action: deny in the PolicyLayer policy for agency-hosting_generateUploadURLV1. 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.

What MCP server provides agency-hosting_generateUploadURLV1? +

agency-hosting_generateUploadURLV1 is provided by the Hostinger Api MCP server (hostinger-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Hostinger Api, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hostinger Api's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.