Get collection entries for an asset collection
AI agents call get_asset_collection_entries 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 collection entries for an asset collection, a pure read operation with no side effects. No data is created, modified, deleted, or financial transactions are involved. The blast radius of misuse is minimal—an attacker could only view collection data they may not be authorized to access, not alter or delete it.
From the tool's definition Tool name 'get_asset_collection_entries' uses 'get' verb and description states 'Get collection entries' — both indicate data retrieval without modification or execution.
Attacks that exploit this kind of access
Get collection entries for an asset collection. 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_asset_collection_entries: 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_asset_collection_entries 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_asset_collection_entries 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_asset_collection_entries. 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_asset_collection_entries 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 →