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.
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.
This tool creates and stores new video data in a project management system, modifying the state of the channel by adding persistent media content. This is a Write operation (reversible via deletion) rather than Destructive.
From the tool's definition Tool description explicitly states 'Upload a video file', which creates new media data. Parameters include 'file_path or file_base64+filename', confirming file creation/upload capability.
Documented attack patterns abuse exactly the kind of access pt_upload_video gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for pt_upload_video:
{
"version": "1",
"default": "deny",
"tools": {
"pt_upload_video": {
"limits": [
{
"counter": "pt_upload_video_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} 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.
Free to start. No card required.
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.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.