List assets via main endpoint (WITHOUT authentication)
AI agents call list_assets 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 or queries asset data from the Red Bee Media streaming platform without modifying, deleting, or executing operations. The lack of authentication combined with the 'list' operation pattern confirms it is a Read category tool with low severity—it only exposes publicly accessible asset information without the ability to cause harm through misuse.
From the tool's definition Tool name 'list_assets' indicates retrieval operation. Description states it 'List assets via main endpoint (WITHOUT authentication)', confirming it retrieves data without side effects.
Attacks that exploit this kind of access
List assets via main endpoint (WITHOUT authentication). 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 list_assets: 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.
list_assets 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 list_assets 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 list_assets. 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.
list_assets 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 →