pt_upload_video
Upload a video file (single-request; use the web UI for files >2 GB). Required: channelId (numeric) OR channel_handle, and either file_path or file_base64+filename. Rate-limited: 5/hour — transcoding is RAM-hot.
This record as markdown: /tools/kh0pper-crow/pt-upload-video.md
What pt_upload_video does on Crow
AI agents use pt_upload_video to create or update resources in Crow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.
Why pt_upload_video is rated Medium
This tool creates new video content in a channel—a reversible write operation. While uploads consume resources (RAM for transcoding) and have rate limits, they don't irreversibly delete data (Destructive), move money (Financial), or execute arbitrary code (Execute). The blast radius is medium: excessive uploads could degrade service or fill storage, but the operation is reversible via deletion.
From the tool's definition Tool description states "Upload a video file" with required parameters for file upload, indicating file creation/modification. Rate limiting and transcoding effects demonstrate side effects that modify the target system.
Attacks that exploit this kind of access
The rule that runs pt_upload_video safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pt_upload_video, this is the rule to start with:
pt_upload_video 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 Crow, apply this rule, and every pt_upload_video call is checked against it from then on.
Questions about pt_upload_video
Upload a video file (single-request; use the web UI for files >2 GB). Required: channelId (numeric) OR channel_handle, and either file_path or file_base64+filename. Rate-limited: 5/hour — transcoding is RAM-hot. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Crow MCP server in PolicyLayer and add a rule for pt_upload_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 Crow. Nothing to install.
pt_upload_video 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 pt_upload_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 pt_upload_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.
pt_upload_video is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
This server
Across the catalogue