Low Risk

live_streaming_get_push_urls

Get push URLs for a stream. Returns RTMP and WHIP push URLs that can be used to push live streams.

How to control live_streaming_get_push_urls ↓

AI agents call live_streaming_get_push_urls to retrieve information from Qiniu MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves (gets) push URLs for streaming—it queries and returns configuration/endpoint data with no side effects on the system, data, or external state. It is purely informational retrieval, fitting the Read category. Severity is low because exposure of this data does not enable unauthorized operations without separate credentials or actions.

From the tool's definition Tool name 'live_streaming_get_push_urls' and description 'Get push URLs for a stream. Returns RTMP and WHIP push URLs' indicate data retrieval without modification.

Documented attack patterns abuse exactly the kind of access live_streaming_get_push_urls 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_get_push_urls:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "live_streaming_get_push_urls": {}
  }
}

live_streaming_get_push_urls is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Qiniu MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the live_streaming_get_push_urls tool do? +

Get push URLs for a stream. Returns RTMP and WHIP push URLs that can be used to push live streams. It is categorised as a Read tool in the Qiniu MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on live_streaming_get_push_urls? +

Register the Qiniu MCP Server MCP server in PolicyLayer and add a rule for live_streaming_get_push_urls: 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.

What risk level is live_streaming_get_push_urls? +

live_streaming_get_push_urls is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit live_streaming_get_push_urls? +

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

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

live_streaming_get_push_urls 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.

Enforce policy on every Qiniu MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.