List all channels in your Twist workspace. Channels are the primary way to organize conversations in Twist, similar to channels in Slack or rooms in other chat applications. This tool retrieves all channels you have access to in the configured workspace. Example response: Found 5 active channels:...
AI agents call get_channels to retrieve information from Langfuse Observability without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that queries and lists existing channels without creating, modifying, deleting, or executing any actions. It has no side effects and minimal blast radius if misused by an AI agent—at worst, an agent learns about available channels it already has access to.
From the tool's definition Tool description states it 'List all channels in your Twist workspace' and 'retrieves all channels you have access to in the configured workspace'. The example response shows it returns channel names and IDs with no modifications or side effects.
Attacks that exploit this kind of access
List all channels in your Twist workspace. Channels are the primary way to organize conversations in Twist, similar to channels in Slack or rooms in other chat applications. This tool retrieves all channels you have access to in the configured workspace. Example response: Found 5 active channels: - #general (ID: 123456) - General team discussions - #engineering (ID: 123457) - Engineering team updates - #product (ID: 123458) - Product development discussions - #support (ID: 123459) - #random (ID: 123460) - Off-topic conversations Use cases: - Discovering available channels when first setting up Twist integration - Finding channel IDs needed for other operations like creating threads - Auditing channel structure and organization - Getting an overview of team communication structure - Identifying channels for specific projects or teams. It is categorised as a Read tool in the Langfuse Observability MCP Server, which means it retrieves data without modifying state.
Register the Langfuse Observability MCP server in PolicyLayer and add a rule for get_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 Langfuse Observability. Nothing to install.
get_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_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_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_channels is provided by the Langfuse Observability MCP server (langfuse-observability-mcp-server). 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 →