hosting_generateUploadURLV1

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 22 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/hosting-generateuploadurlv1.md

WHAT IT DOES

What hosting_generateUploadURLV1 does on Hostinger Api

AI agents use 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.

Parameter	Type	Required	Description
`domain`	string	Yes	Website domain
`username`	string	Yes	Account username

Parameters from the server's own tool schema.

RISK

Why hosting_generateUploadURLV1 is rated Medium

Creates files in website storage; reversible via deletion but high impact if abused for malicious payloads.

From the tool's definition Generate upload URL, uploading files directly to website's public_html directory

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hosting_generateUploadURLV1 safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger Api, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hosting_generateUploadURLV1, this is the rule to start with:

hosting_generateUploadURLV1 Rate-limited

hosting_generateUploadURLV1 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hosting_generateUploadURLV1": {
      "limits": [
        {
          "counter": "hosting_generateuploadurlv1_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every hosting_generateUploadURLV1 call is checked against it from then on.

FAQ

Questions about hosting_generateUploadURLV1

What does the hosting_generateUploadURLV1 tool do? +

Generate a file browser upload URL with authentication credentials for uploading files directly to a website's file storage. Returns url, auth_key and rest_auth_key. Use these to upload a file to the website's public_html directory 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 public_html, 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 hosting_generateUploadURLV1 accept? +

hosting_generateUploadURLV1 accepts 2 parameters: domain, username. Required: domain, username. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on hosting_generateUploadURLV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for 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 hosting_generateUploadURLV1? +

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

Can I rate-limit hosting_generateUploadURLV1? +

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

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

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.

KEEP EXPLORING

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

This server

All 382 Hostinger Api tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →