Upload a LOCAL file (image, video, or audio) from this machine and get back a public https URL. Use the returned url as an input for vicsee_generate — e.g. drop it into reference_image_urls for a reference-to-video storyboard, or image_urls for image-to-video. PREFER this over inline base64 for r...
AI agents use vicsee_upload to create or update resources in Vicsee — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vicsee environment.
This tool creates new resources (uploaded files) in persistent storage with a retrievable public URL, which is a reversible write operation. While uploads are generally safe, the public accessibility of generated URLs and potential for storing unwanted content elevates severity to medium. Not Destructive (reversible), not Execute (no code/command execution), not Financial.
From the tool's definition Tool 'uploads' files and returns a 'public https URL', storing file content in persistent storage. Description explicitly states 'The file uploads directly to storage'.
Attacks that exploit this kind of access
Upload a LOCAL file (image, video, or audio) from this machine and get back a public https URL. Use the returned url as an input for vicsee_generate — e.g. drop it into reference_image_urls for a reference-to-video storyboard, or image_urls for image-to-video. PREFER this over inline base64 for references: large base64 strings get truncated in tool-call output and the model rejects them. The file uploads directly to storage; only its public URL comes back. It is categorised as a Write tool in the Vicsee MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vicsee MCP server in PolicyLayer and add a rule for vicsee_upload: 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 Vicsee. Nothing to install.
vicsee_upload 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 vicsee_upload 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 vicsee_upload. 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.
vicsee_upload is provided by the Vicsee MCP server (vicseeai/vicsee-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →