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 Playwright Stealth 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 query of channel metadata. It retrieves information about available channels without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal — an agent could discover channel names and IDs but cannot cause harm through this tool alone.
From the tool's definition Tool name is 'get_channels' and description states it 'retrieves all channels you have access to' and 'List all channels in your Twist workspace' — purely a query/list operation with no data modification or side effects.
Documented attack patterns abuse exactly the kind of access get_channels gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Playwright Stealth, and nothing reaches the server without passing your rules. This is the rule we recommend for get_channels:
{
"version": "1",
"default": "deny",
"tools": {
"get_channels": {}
}
}get_channels is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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 Playwright Stealth MCP Server, which means it retrieves data without modifying state.
Register the Playwright Stealth 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 Playwright Stealth. 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 Playwright Stealth MCP server (pulsemcp/mcp-servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Playwright Stealth, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
68 Playwright Stealth tools catalogued and risk-classified — across an index of 43,000+ MCP servers.