start_live_event

Put a live event on air (start streaming). The event must be bound to an encoder.

SERVERZype Com SOURCEzype/zype-mcp

High RISK CLASS

Category Execute

Parameters 11 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/start-live-event.md

WHAT IT DOES

What start_live_event does on Zype Com

AI agents invoke start_live_event to trigger actions in Zype Com. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`live_event_id`	string	Yes	The unique ID of the live event (required)

Parameters from the server's own tool schema.

RISK

Why start_live_event is rated High

start_live_event triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

start_live_event Rate-limited

start_live_event stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_live_event": {
      "limits": [
        {
          "counter": "start_live_event_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 start_live_event call is checked against it from then on.

FAQ

Questions about start_live_event

What does the start_live_event tool do? +

Put a live event on air (start streaming). The event must be bound to an encoder. It is categorised as a Execute tool in the Zype Com MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does start_live_event accept? +

start_live_event accepts 1 parameter: live_event_id. Required: live_event_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on start_live_event? +

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

start_live_event is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_live_event? +

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

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

start_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 → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →