Multi-search V3 for assets, tags, and participants with advanced filtering
AI agents call search_multi_v3 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 data (assets, tags, participants) from the Red Bee Media OTT platform with no side effects. It performs searches and filtering only, which is characteristic of Read category tools. No data creation, modification, deletion, or financial transaction is implied.
From the tool's definition Tool is named 'search_multi_v3' and described as 'Multi-search V3 for assets, tags, and participants with advanced filtering'. The name 'search' and description explicitly indicate retrieval/querying operations without modification.
Attacks that exploit this kind of access
Multi-search V3 for assets, tags, and participants with advanced filtering. 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 search_multi_v3: 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.
search_multi_v3 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 search_multi_v3 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 search_multi_v3. 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.
search_multi_v3 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 →