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...
Risk signalsHigh parameter count (39 properties)
Part of the Zype Com server.
Free to start. No card required.
AI agents use update_video to create or modify resources in Zype Com. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call update_video repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Zype Com.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"update_video": {
"limits": [
{
"counter": "update_video_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Zype Com policy for all 76 tools.
These attack patterns abuse exactly the kind of access update_video gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
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.
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.
update_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 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.
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.
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.
Deterministic rules across all 76 Zype Com tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.