Bind a playback domain to a LiveStreaming bucket for live streaming. This allows you to configure the domain for playing back streams via FLV/M3U8/WHEP.
AI agents use live_streaming_bind_play_domain to create or update resources in Qiniu MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Qiniu MCP Server environment.
This tool creates or modifies domain bindings within the live streaming service, which is a reversible Write operation. While it configures infrastructure, it does not execute arbitrary code, delete data, or move funds. The severity is medium because misconfiguration could disrupt streaming services or redirect traffic, but the operation is reversible and limited to domain binding configuration.
From the tool's definition Tool name contains 'bind' and description states 'Bind a playback domain to a LiveStreaming bucket' and 'configure the domain', indicating configuration modification of streaming infrastructure.
Documented attack patterns abuse exactly the kind of access live_streaming_bind_play_domain gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Qiniu MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for live_streaming_bind_play_domain:
{
"version": "1",
"default": "deny",
"tools": {
"live_streaming_bind_play_domain": {
"limits": [
{
"counter": "live_streaming_bind_play_domain_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}live_streaming_bind_play_domain 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.
Free to start. No card required.
Bind a playback domain to a LiveStreaming bucket for live streaming. This allows you to configure the domain for playing back streams via FLV/M3U8/WHEP. It is categorised as a Write tool in the Qiniu MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Qiniu MCP Server MCP server in PolicyLayer and add a rule for live_streaming_bind_play_domain: 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 Qiniu MCP Server. Nothing to install.
live_streaming_bind_play_domain is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the live_streaming_bind_play_domain 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.
Set action: deny in the PolicyLayer policy for live_streaming_bind_play_domain. 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.
live_streaming_bind_play_domain is provided by the Qiniu MCP Server MCP server (qiniu/qiniu-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 24 Qiniu MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
24 Qiniu MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.