Retrieves unique asset tags for a given type (e.g., country origin for movies)
AI agents call get_assets_by_tag 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 queries and returns asset metadata (tags/classifications) without side effects. It performs a read-only lookup operation on the streaming platform's content library. No data is created, modified, deleted, or financial transactions are involved. The blast radius of misuse is minimal—an agent could only enumerate asset tags, which is low-risk information retrieval.
From the tool's definition Tool name 'get_assets_by_tag' and description 'Retrieves unique asset tags for a given type' clearly indicate a data retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Retrieves unique asset tags for a given type (e.g., country origin for movies). 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_assets_by_tag: 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_assets_by_tag 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_assets_by_tag 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_assets_by_tag. 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_assets_by_tag 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 →