Get list of active channels on the platform
AI agents call get_active_channels 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 a list of active channels, which is a read-only operation that queries existing data without creating, modifying, deleting, or executing anything. There is no financial impact, no code execution, and no destructive action. The low severity reflects minimal risk even if misused by an agent—it simply returns information about available channels.
From the tool's definition Tool name 'get_active_channels' and description 'Get list of active channels on the platform' indicate a query/retrieval operation that retrieves channel information without modification or side effects.
Attacks that exploit this kind of access
Get list of active channels on the platform. 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_active_channels: 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_active_channels 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_active_channels 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_active_channels. 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_active_channels 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 →