createPageClip
Turns a page — or one section of it — into a short animated video (6–20 s; 9:16, 1:1 or 16:9) using only the page's own words, prices and Library pictures. Without quote_hash it answers the QUOTE: the scenes, the credits per second and the total, and your balance. Send the same options with that ...
This record as markdown: /tools/vipcasso-mcp/createpageclip.md
What createPageClip does on Vipcasso
AI agents use createPageClip 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 createPageClip is rated Medium
An AI agent can call createPageClip 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 createPageClip 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 createPageClip, this is the rule to start with:
createPageClip 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 createPageClip call is checked against it from then on.
Questions about createPageClip
Turns a page — or one section of it — into a short animated video (6–20 s; 9:16, 1:1 or 16:9) using only the page's own words, prices and Library pictures. Without quote_hash it answers the QUOTE: the scenes, the credits per second and the total, and your balance. Send the same options with that quote_hash to APPROVE: the clip is queued (202) and lands in your Library as a video. Credits are taken once, when the video is made; a clip that fails costs nothing. A changed page or price is refused with the new quote (409); a short balance with 402. Honours Idempotency-Key; approving the same quote again while it is being made returns that job (200). 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.
createPageClip 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 createPageClip: 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.
createPageClip 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 createPageClip 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 createPageClip. 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.
createPageClip 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