update_live_encoder

SERVERZype Com SOURCEzype/zype-mcp

Medium RISK CLASS

Category Write

Parameters 101 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-live-encoder.md

WHAT IT DOES

What update_live_encoder does on Zype Com

AI agents use update_live_encoder 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
`name`	string	—	Encoder / channel name
`region`	string	—	AWS region the encoder runs in (set at creation)
`encoder_id`	string	Yes	The unique ID of the live encoder to update (required)
`live_inputs`	array	—	Live inputs (RTMP ingest sources) to create/update/remove
`nielsen_tagging`	boolean	—	Whether Nielsen watermark tagging is enabled
`event_profile_id`	string	—	Event profile ID defining the encoding presets
`live_destinations`	array	—	Live destinations (HLS/RTMP outputs) to create/update/remove
`nielsen_distributor_id`	string	—	Nielsen distributor ID (when tagging is enabled)
`high_availability_enabled`	boolean	—	Whether the encoder runs in high-availability mode
`mqcs_input_switch_enabled`	boolean	—	Whether MQCS automatic input switching is enabled

Parameters from the server's own tool schema.

RISK

Why update_live_encoder is rated Medium

An AI agent can call update_live_encoder 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 signalsAccepts URL/endpoint input (live_inputs[].hostname) · Handles credentials or secrets (live_destinations[].password) · High parameter count (33 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_live_encoder Rate-limited

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

FAQ

Questions about update_live_encoder

What does the update_live_encoder tool do? +

Update an existing live encoder. Only the fields you provide are changed. To modify inputs/destinations, pass live_inputs/live_destinations: include an item's id to update it, set _destroy: true (with id) to remove it, or omit id to add a new one. Note: a running encoder only accepts a limited set of edits. 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_live_encoder accept? +

update_live_encoder accepts 10 parameters: name, region, encoder_id, live_inputs, nielsen_tagging, event_profile_id, live_destinations, nielsen_distributor_id, high_availability_enabled, mqcs_input_switch_enabled. Required: encoder_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_live_encoder? +

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

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

Can I rate-limit update_live_encoder? +

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

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

update_live_encoder 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

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

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