This record as markdown: /tools/io-github-portel-dev-ncp/upload-video.md
What upload_video does on Ncp
AI agents use upload_video to create or update resources in Ncp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ncp environment.
Why upload_video is rated Medium
This tool creates new data (uploads a video) on an external platform. While the upload itself is a write operation that modifies YouTube's state, it is reversible (the video can be deleted or made private). It does not move money (not Financial), does not execute arbitrary code (not Execute), and does not irreversibly destroy data (not Destructive).
From the tool's definition Tool name: 'upload_video'. Description: 'Upload video to YouTube'. The tool creates/adds new media content to a platform (YouTube), which is a reversible write operation.
Attacks that exploit this kind of access
The rule that runs upload_video safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For upload_video, this is the rule to start with:
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 Ncp, apply this rule, and every upload_video call is checked against it from then on.
Questions about upload_video
Upload video to YouTube. It is categorised as a Write tool in the Ncp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ncp MCP server in PolicyLayer and add a rule for 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 Ncp. Nothing to install.
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 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 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.
upload_video is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue