update_video

SERVERZype Com SOURCEzype/zype-mcp

Medium RISK CLASS

Category Write

Parameters 120 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/com-zype-mcp-server/update-video.md

WHAT IT DOES

What update_video does on Zype Com

AI agents use update_video to create or update resources in Zype Com, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zype Com environment.

Parameter	Type	Required	Description
`genre`	string	—	Genre
`title`	string	—	Video title
`active`	boolean	—	Active status
`on_air`	boolean	—	On-air status
`rating`	string	—	Content rating
`season`	number	—	Season number
`country`	string	—	Country code
`episode`	number	—	Episode number
`featured`	boolean	—	Featured status
`keywords`	array	—	Keywords/tags
`language`	string	—	Language code
`plan_ids`	array	—	Plan IDs granting access

Parameters from the server's own tool schema.

RISK

Why update_video is rated Medium

An AI agent can call update_video faster than any human can review: one bad instruction and it creates or modifies resources in Zype Com by the hundred, each call as confident as the last.

Risk signalsHigh parameter count (39 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_video safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Zype Com, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_video, this is the rule to start with:

update_video Rate-limited

update_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_video": {
      "limits": [
        {
          "counter": "update_video_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Zype Com, apply this rule, and every update_video call is checked against it from then on.

FAQ

Questions about update_video

What does the update_video tool do? +

Update a video's metadata. Only provided fields are updated. Supports all fields from create_video plus: - To add a category: provide categories array with {category_id, value} objects (call list_categories first to get the category_id). Omit id when adding. - To update an existing category entry: include the entry's id (from get_video) along with category_id and value. Without id, you'll create a duplicate entry. - To schedule auto-enable/disable: use enable_at, disable_at - To set monetization: subscription_required, purchase_price, etc. - To link to series: series_id, season, episode Example add: {"video_id": "...", "categories": [{"category_id": "6439b285101efc0001a067aa", "value": ["true"]}]} Example update existing: {"video_id": "...", "categories": [{"id": "<entry id from get_video>", "category_id": "6439b285101efc0001a067aa", "value": ["false"]}]}. It is categorised as a Write tool in the Zype Com MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_video accept? +

update_video accepts 12 parameters: genre, title, active, on_air, rating, season, country, episode, featured, keywords, language, plan_ids. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_video? +

Register the Zype Com MCP server in PolicyLayer and add a rule for update_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 Zype Com. Nothing to install.

What risk level is update_video? +

update_video is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_video? +

Yes. Add a rate_limit block to the update_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.

How do I block update_video completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_video? +

update_video is provided by the Zype Com MCP server (zype/zype-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Zype Com, and thousands of servers like it.

This server

All 296 Zype Com tools →

Across the catalogue

generate_video_title on YouTube MCP Server →aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →