How do I let an AI agent use my video tool account without losing control?
By RemixViral · Last updated · Markdown version
Give the agent its own credential with the fewest permissions that work, prefer read-only tools, cap what it can spend, keep a list of connected agents you can revoke in one click, and rely on your client's confirmation prompts for anything that costs money. Check each of those controls actually exists in the tool before you connect.
Why this happens
An agent that can call a tool can do whatever that tool and its credential allow, at machine speed, based on instructions it may have picked up from text it read. The Model Context Protocol security guidance names the cost of broad credentials directly: a stolen token carrying wide scopes expands the blast radius, makes revocation disruptive, and, in its words, a single omnibus scope "masks user intent per operation".
The risk is not only theft. A well-meaning agent can loop, retry a failed call, or misread a vague instruction and spend credits or delete data. The protocol does not enforce a user-interaction model, but the MCP tools specification says that for trust and safety there "SHOULD always be a human in the loop with the ability to deny tool invocations", and that applications should present confirmation prompts. Whether that happens is up to the client you use, not the server.
So control has two layers: what the account lets the credential do (permissions, limits, balance, revocation), and what the client asks you before acting. A safe setup does not depend on only one of them.
A vendor-neutral checklist, then how RemixViral maps to it
Apply the checklist to any video tool before you connect an agent. The mapping after it states what RemixViral does today and where it does not.
1. Use least-privilege scopes
Create the credential with only the scopes the job needs. Start with read-only. In RemixViral, scopes are set per API key (video:read, video:create, credits:read, usage:read and others). A key without video:create cannot create videos. The default key scopes are video:create, video:read, credits:read and usage:read; remove video:create if the agent only needs to read.
2. Give each agent its own key or connection
One credential per agent makes it possible to see what each did and to revoke one without breaking the rest. With RemixViral's OAuth flow, each connection becomes its own API key named "MCP: <client name>" on your account, with a 90-day expiry. If you use a manual key, create a separate one per agent at the developer page.
3. Approve the connection yourself, and know where to revoke
OAuth connection shows a consent screen with the client name and what it can do, and nothing connects until you press Allow. Dashboard, API keys lists every key with its name, scopes and last-used time. Revoking or deleting a key cuts the agent off on its next call.
4. Prefer read-only tools and know the one that spends
Of RemixViral's seven MCP tools, six are annotated read-only: list_clip_jobs, get_clip_job, list_videos, get_video, list_niches and get_credit_balance. create_video is annotated readOnlyHint false, destructiveHint false, idempotentHint false, so a client that honours those hints asks you before running it. There is no MCP tool that deletes anything, uploads a video, starts a clip job, buys credits or changes the plan.
5. Bound the spend
Spending is prepaid credits: create_video is refused up front when your balance is short, so the balance is the practical cap. Keep it small if the agent is new. At most three faceless videos can render at once, and an identical create_video request within 10 minutes returns the existing video and spends nothing.
6. Limit request rate and review the log
Each API key has its own request limit, 100 requests per hour by default, after which calls fail with RATE_LIMIT_EXCEEDED. Videos the agent creates appear in your dashboard Videos list, and per-key usage is shown in the developer portal.
7. Never paste a key into a prompt or a chat
Put the key in your client's secret or environment configuration, or use OAuth so no key is typed at all. A key in a prompt can be logged, shared and read by the model. If one leaks, revoke it and create another.
Gaps to plan around
There is no approval queue inside RemixViral. If your MCP client does not prompt before running a tool that is not read-only, create_video will run when the agent decides to call it, and the only limit is your balance. Test your client with a harmless tool first, and check whether it shows a confirmation.
There is also no separate spending cap per key. If you need a hard limit, keep the credit balance low and top up deliberately. And scopes control what a key can call; they do not stop an agent from asking for the wrong topic.
| Control | Exists in RemixViral? | Detail |
|---|---|---|
| Per-key scopes | Yes | Scopes are set per key; a key without video:create cannot create videos |
| Separate credential per agent | Yes | OAuth connections become keys named "MCP: <client>"; manual keys are created one by one |
| Consent screen | Yes | OAuth shows the client and permissions with Allow and Cancel |
| Revoke | Yes | Dashboard, API keys; takes effect on the agent's next call |
| Last-use visibility | Yes | Last used time per key; per-key usage in the developer portal |
| Per-key request limit | Yes | 100 requests per hour by default |
| Spend cap | Partly | The prepaid balance is the cap; there is no separate per-key spend cap |
| Per-action approval queue | No | Confirmation depends on your MCP client honouring the read-only hints |
| Delete, upload or buy tools | None exist | The server exposes none of them |
RemixViral rows come from our own documentation at /en/mcp; the MCP specification wording is from the pages in the sources.
When to use RemixViral
RemixViral's agent access suits a person who wants an assistant to read the ranked clips of videos they uploaded and, if they choose, start a faceless Short, while they stay in charge.
It fits when
- Read-only supervision: the assistant lists clip jobs and summarises ranked clips with times, scores and reasons; you decide in the web app.
- Bounded creation: a key with video:create, a small prepaid balance, and a client that asks before the one spending tool.
- Revocable access: you can see every connection and cut it off.
It is not the right tool when
- You need per-action approvals enforced by the server, spend limits per key or role-based access for a team: RemixViral does not have these, and has no team seats; look for a platform with an approval workflow or enterprise access controls.
- You want the agent to upload, post or delete: RemixViral exposes none of these tools.
Ask your AI assistant to do it
Before giving the agent any spending power, have it report what it can see and what it would cost.
Assign to RemixViral: use get_credit_balance to read my balance and plan, then list_videos to show the videos you created so far, and list the MCP tools you can call. Do not call create_video. Show me what you found so I can approve whether to allow video creation.How to connect RemixViral to Claude, ChatGPT, Cursor or Gemini, and the full tool list: AI assistants (MCP).
Frequently asked questions
Can I give an agent read-only access to RemixViral?
Yes. Create an API key without the video:create scope and the agent can only call the read tools. Six of the seven MCP tools are read-only; only create_video spends credits.
How do I cut an agent off immediately?
Revoke or delete its key in Dashboard, API keys. OAuth connections appear there as "MCP: <client name>". The agent loses access on its next call.
Is there a spending limit per agent?
No separate one. Spending is limited by your prepaid credit balance, and create_video is refused up front when the balance is short. Keep the balance low for a new agent.
Will my AI client ask before it spends credits?
Only if the client honours the tool annotations. RemixViral marks create_video as not read-only so clients that respect the hints should ask first, but RemixViral has no approval queue of its own.
Sources
Related: RemixViral over MCP: tools and oversight · Why does my agent get INSUFFICIENT_CREDITS or 429? · Which AI video clipper works with Claude over MCP? · Developers and API keys