neuron_studio_transform_video
Run an AI transform on a hosted video via Replicate (async): op 'bg-remove' or 'face-swap' (face-swap needs imageUrl). Returns { id, status } — poll neuron_studio_transform_video_status for videoUrl. Needs the matching model version configured.
This record as markdown: /tools/io-github-conquext-neuron/neuron-studio-transform-video.md
What neuron_studio_transform_video does on Neuron
AI agents invoke neuron_studio_transform_video to trigger actions in Neuron. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
op | string | Yes | Which transform. |
imageUrl | string | — | Reference face image (face-swap only). |
videoUrl | string | Yes | Source video URL. |
Parameters from the server's own tool schema.
Why neuron_studio_transform_video is rated High
neuron_studio_transform_video triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs neuron_studio_transform_video safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Neuron, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For neuron_studio_transform_video, this is the rule to start with:
neuron_studio_transform_video stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_studio_transform_video call is checked against it from then on.
Questions about neuron_studio_transform_video
Run an AI transform on a hosted video via Replicate (async): op 'bg-remove' or 'face-swap' (face-swap needs imageUrl). Returns { id, status } — poll neuron_studio_transform_video_status for videoUrl. Needs the matching model version configured. It is categorised as a Execute tool in the Neuron MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
neuron_studio_transform_video accepts 3 parameters: op, imageUrl, videoUrl. Required: op, videoUrl. The full parameter table on this page comes from the server's own tool schema.
Register the Neuron MCP server in PolicyLayer and add a rule for neuron_studio_transform_video: 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 Neuron. Nothing to install.
neuron_studio_transform_video is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the neuron_studio_transform_video 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 neuron_studio_transform_video. 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.
neuron_studio_transform_video is provided by the Neuron MCP server (neuron-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Neuron, and thousands of servers like it.
Across the catalogue