bulk_generate_ai_metadata

SERVERZype Com SOURCEzype/zype-mcp

Medium RISK CLASS

Category Write

Parameters 41 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/bulk-generate-ai-metadata.md

WHAT IT DOES

What bulk_generate_ai_metadata does on Zype Com

AI agents use bulk_generate_ai_metadata 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
`confirm`	boolean	—	Set to true to confirm overwriting metadata on every listed video (required in safe mode)
`video_ids`	array	Yes	Video IDs to generate and apply metadata for (required) - these videos WILL be modified
`attributes`	array	—	Attributes to generate: title, friendly_title, description, short_description, keywords, genre. Omit for Zype defaults.
`prompt_context_id`	string	—	Optional prompt context ID (brand voice / style guide configured in Zype) to steer generation

Parameters from the server's own tool schema.

RISK

Why bulk_generate_ai_metadata is rated Medium

An AI agent can call bulk_generate_ai_metadata 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 signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bulk_generate_ai_metadata 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 bulk_generate_ai_metadata, this is the rule to start with:

bulk_generate_ai_metadata Rate-limited

bulk_generate_ai_metadata 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": {
    "bulk_generate_ai_metadata": {
      "limits": [
        {
          "counter": "bulk_generate_ai_metadata_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 bulk_generate_ai_metadata call is checked against it from then on.

FAQ

Questions about bulk_generate_ai_metadata

What does the bulk_generate_ai_metadata tool do? +

Generate AI metadata for many videos AND WRITE IT DIRECTLY ONTO THEM. WARNING - THIS IS NOT A SUGGESTION-ONLY TOOL. Unlike generate_ai_metadata, the bulk endpoint overwrites each video's metadata with the generated values. There is no review step, no suggestion to inspect, and no undo through the API. - Runs asynchronously in the background; returns only a queued count - Every listed video is modified once processing completes - In safe mode this requires confirm: true - Use generate_ai_metadata per video if you want to review before writing - Each video needs a completed transcript, otherwise it is skipped or errors. 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 bulk_generate_ai_metadata accept? +

bulk_generate_ai_metadata accepts 4 parameters: confirm, video_ids, attributes, prompt_context_id. Required: video_ids. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on bulk_generate_ai_metadata? +

Register the Zype Com MCP server in PolicyLayer and add a rule for bulk_generate_ai_metadata: 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 bulk_generate_ai_metadata? +

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

Can I rate-limit bulk_generate_ai_metadata? +

Yes. Add a rate_limit block to the bulk_generate_ai_metadata 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 bulk_generate_ai_metadata completely? +

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

bulk_generate_ai_metadata 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_commit on MCP Server PR Pilot →generate_summary on ACE-MCP →generate_video_title on YouTube MCP Server →generate_devtools_report on Percepta MCP Server → The MCP Attack Database →

Guides

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