approveSiteMissingImages
Approve the quote at one quality: its tier (standard by default, or premium) and that tier's quote_hash. One picture is made per empty place at that quality and price, kept in your Library and put in its place on the page (a draft edit; the live site shows it after the next publish). Credits are ...
This record as markdown: /tools/vipcasso-mcp/approvesitemissingimages.md
What approveSiteMissingImages does on Vipcasso
AI agents use approveSiteMissingImages to create or update resources in Vipcasso, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vipcasso environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | object | — | |
files | array | — | |
query | object | — | |
fields | object | — | |
path_params | object | — |
Parameters from the server's own tool schema.
Why approveSiteMissingImages is rated Medium
An AI agent can call approveSiteMissingImages faster than any human can review: one bad instruction and it creates or modifies resources in Vipcasso by the hundred, each call as confident as the last.
Risk signalsAccepts file system path (files[].filename) · Accepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs approveSiteMissingImages safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vipcasso, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For approveSiteMissingImages, this is the rule to start with:
approveSiteMissingImages 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 Vipcasso, apply this rule, and every approveSiteMissingImages call is checked against it from then on.
Questions about approveSiteMissingImages
Approve the quote at one quality: its tier (standard by default, or premium) and that tier's quote_hash. One picture is made per empty place at that quality and price, kept in your Library and put in its place on the page (a draft edit; the live site shows it after the next publish). Credits are taken per picture made; a picture that fails costs nothing. A changed site, price or price of a credit — or a hash shown for the other tier — is refused with the new quote (409); a short balance with 402. Honours Idempotency-Key; a second approval while pictures are being made returns the same job. It is categorised as a Write tool in the Vipcasso MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
approveSiteMissingImages accepts 5 parameters: body, files, query, fields, path_params. The full parameter table on this page comes from the server's own tool schema.
Register the Vipcasso MCP server in PolicyLayer and add a rule for approveSiteMissingImages: 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 Vipcasso. Nothing to install.
approveSiteMissingImages 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 approveSiteMissingImages 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 approveSiteMissingImages. 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.
approveSiteMissingImages is provided by the Vipcasso MCP server (@vipcasso/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vipcasso, and thousands of servers like it.
This server
Across the catalogue