Retrieves playback information (stream URL, DRM, subtitles) for an asset
AI agents call get_playback_info to retrieve information from Red Bee MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata and streaming details required to play content (stream URL, DRM parameters, subtitle options) but does not create, modify, delete, or execute operations. It has minimal blast radius—the information returned is needed for normal playback functionality and does not enable financial transactions, destructive actions, or code execution. Classification as Read is appropriate.
From the tool's definition Tool name 'get_playback_info' and description 'Retrieves playback information (stream URL, DRM, subtitles) for an asset' indicate a query/fetch operation with no data modification or deletion.
Attacks that exploit this kind of access
Retrieves playback information (stream URL, DRM, subtitles) for an asset. It is categorised as a Read tool in the Red Bee MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Red Bee MCP Server MCP server in PolicyLayer and add a rule for get_playback_info: 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 Red Bee MCP Server. Nothing to install.
get_playback_info 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_playback_info 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_playback_info. 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_playback_info is provided by the Red Bee MCP Server MCP server (tamsi/redbee-mcp). 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 →