playout_update_hls_profile

Update HLS Profile. Playout Scheduler (HLS Profiles).

SERVERZype Com SOURCEzype/zype-mcp

Medium RISK CLASS

Category Write

Parameters 21 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/playout-update-hls-profile.md

WHAT IT DOES

What playout_update_hls_profile does on Zype Com

AI agents use playout_update_hls_profile 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
`id`	string	Yes	id (required)
`body`	object	—	Request body fields for this operation

Parameters from the server's own tool schema.

RISK

Why playout_update_hls_profile is rated Medium

An AI agent can call playout_update_hls_profile 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 raw HTML/template content (body)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

playout_update_hls_profile Rate-limited

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

FAQ

Questions about playout_update_hls_profile

What does the playout_update_hls_profile tool do? +

Update HLS Profile. Playout Scheduler (HLS Profiles). 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 playout_update_hls_profile accept? +

playout_update_hls_profile accepts 2 parameters: id, body. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on playout_update_hls_profile? +

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

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

Can I rate-limit playout_update_hls_profile? +

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

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

playout_update_hls_profile 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 →