AI agents call get_stream_url to retrieve information from Luxxon without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
get_stream_url retrieves and returns a URL pointer to live video stream data for consumption by agents with their own WebRTC stack. It queries and reads existing session state without side effects—no data is created, modified, deleted, or executed.
From the tool's definition Tool returns a WHEP playback URL for an existing LIVE session — 'Return a WHEP playback URL' — which is a retrieval operation that provides access to a video stream without modifying state, creating new resources, or triggering external operations beyond…
Attacks that exploit this kind of access
Return a WHEP playback URL for a LIVE session. For agents with their own WebRTC stack; most agents should prefer get_frame instead. It is categorised as a Read tool in the Luxxon MCP Server, which means it retrieves data without modifying state.
Register the Luxxon MCP server in PolicyLayer and add a rule for get_stream_url: 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 Luxxon. Nothing to install.
get_stream_url is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_stream_url 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 get_stream_url. 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.
get_stream_url is provided by the Luxxon MCP server (luxxon-dev/luxxon-sdk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →