teams_list_channels
Lists channels in a Microsoft Teams workspace. Returns channels that are cached in the local Teams client. If the result is empty, the channels have not been loaded into the local cache yet — ask the user to open Microsoft Teams and browse to the team's channels, then try again.
This record as markdown: /tools/com-local-mcp-local-mcp/teams-list-channels.md
What teams_list_channels does on Local
AI agents call teams_list_channels to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
team_id | string | Yes | Team ID from list_teams |
Parameters from the server's own tool schema.
Why teams_list_channels is rated Low
This tool retrieves and queries existing data from the local Teams client without creating, modifying, deleting, or executing any operations. It has no blast radius—listing channels is informational only and cannot cause harm even if misused by an AI agent.
From the tool's definition Tool name 'teams_list_channels' and description 'Lists channels in a Microsoft Teams workspace' indicate a retrieval operation with no data modification.
Attacks that exploit this kind of access
The rule that runs teams_list_channels safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For teams_list_channels, this is the rule to start with:
teams_list_channels is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every teams_list_channels call is checked against it from then on.
Questions about teams_list_channels
Lists channels in a Microsoft Teams workspace. Returns channels that are cached in the local Teams client. If the result is empty, the channels have not been loaded into the local cache yet — ask the user to open Microsoft Teams and browse to the team's channels, then try again. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
teams_list_channels accepts 1 parameter: team_id. Required: team_id. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for teams_list_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 Local. Nothing to install.
teams_list_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 teams_list_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 teams_list_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.
teams_list_channels is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue