channels_navigateList
Navigate within an existing list session (prev/next page, jump to specific page)
This record as markdown: /tools/cowork-bench/channels-navigatelist.md
What channels_navigateList does on Cowork Bench
AI agents invoke channels_navigateList to trigger actions in Cowork Bench. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why channels_navigateList is rated High
channels_navigateList triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs channels_navigateList safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cowork Bench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For channels_navigateList, this is the rule to start with:
channels_navigateList stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cowork Bench, apply this rule, and every channels_navigateList call is checked against it from then on.
Questions about channels_navigateList
Navigate within an existing list session (prev/next page, jump to specific page). It is categorised as a Execute tool in the Cowork Bench MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cowork Bench MCP server in PolicyLayer and add a rule for channels_navigateList: 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 Cowork Bench. Nothing to install.
channels_navigateList is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the channels_navigateList 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 channels_navigateList. 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.
channels_navigateList is provided by the Cowork Bench MCP server (0717376/cowork_bench). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cowork Bench, and thousands of servers like it.
Across the catalogue