create_live_event

SERVERZype Com SOURCEzype/zype-mcp

Medium RISK CLASS

Category Write

Parameters 121 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/create-live-event.md

WHAT IT DOES

What create_live_event does on Zype Com

AI agents use create_live_event 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
`title`	string	Yes	Title of the live event
`on_air_at`	string	—	Scheduled on-air time (ISO 8601)
`encoder_id`	string	—	Alias for video_source_id — the encoder backing this event
`event_type`	string	—	Live event type (e.g. the encoder/streaming mode)
`off_air_at`	string	—	Scheduled off-air time (ISO 8601)
`description`	string	—	Description of the live event
`auto_archive`	boolean	—	Whether to automatically archive the stream to a VOD when it ends
`encoder_name`	string	—	Legacy: encoder hostname used to resolve the video source when no ID is given
`rental_price`	number	—	Rental price
`pass_required`	boolean	—	Whether a pass is required to watch
`purchase_price`	number	—	Purchase price
`rental_duration`	number	—	Rental duration in hours

Parameters from the server's own tool schema.

RISK

Why create_live_event is rated Medium

An AI agent can call create_live_event 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 (18 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

create_live_event Rate-limited

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

FAQ

Questions about create_live_event

What does the create_live_event tool do? +

Create a new live event (MSL live stream). Provide a title and bind it to a Zype Live encoder via video_source_id (or encoder_id / legacy encoder_name). Optionally set the on-air/off-air schedule, archiving behavior, and monetization requirements. 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 create_live_event accept? +

create_live_event accepts 12 parameters: title, on_air_at, encoder_id, event_type, off_air_at, description, auto_archive, encoder_name, rental_price, pass_required, purchase_price, rental_duration. Required: title. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_live_event? +

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

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

Can I rate-limit create_live_event? +

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

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

create_live_event 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

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

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