ecommerce_createAProductImageUploadURLV1
Returns a signed URL to upload a product image to (multipart/form-data POST). Then call the attach-image endpoint with the returned object_name to scan and attach it to the product.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/ecommerce-createaproductimageuploadurlv1.md
What ecommerce_createAProductImageUploadURLV1 does on Hostinger Api
AI agents use ecommerce_createAProductImageUploadURLV1 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 |
|---|---|---|---|
store_id | string | Yes | The ID of the store the product belongs to. |
product_id | string | Yes | The ID of the product the image will be attached to. |
Parameters from the server's own tool schema.
Why ecommerce_createAProductImageUploadURLV1 is rated Medium
Creates and uploads product image data reversibly; moderate blast radius if misused to deface products.
From the tool's definition upload product image, signed URL, attach to product
Attacks that exploit this kind of access
The rule that runs ecommerce_createAProductImageUploadURLV1 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 ecommerce_createAProductImageUploadURLV1, this is the rule to start with:
ecommerce_createAProductImageUploadURLV1 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 Hostinger Api, apply this rule, and every ecommerce_createAProductImageUploadURLV1 call is checked against it from then on.
Questions about ecommerce_createAProductImageUploadURLV1
Returns a signed URL to upload a product image to (multipart/form-data POST). Then call the attach-image endpoint with the returned object_name to scan and attach it to the product. 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.
ecommerce_createAProductImageUploadURLV1 accepts 2 parameters: store_id, product_id. Required: store_id, product_id. The full parameter table on this page comes from the server's own tool schema.
Register the Hostinger Api MCP server in PolicyLayer and add a rule for ecommerce_createAProductImageUploadURLV1: 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.
ecommerce_createAProductImageUploadURLV1 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 ecommerce_createAProductImageUploadURLV1 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 ecommerce_createAProductImageUploadURLV1. 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.
ecommerce_createAProductImageUploadURLV1 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.
This server
Across the catalogue