Low Risk

teams_list_channels

List channels in a team

How to control teams_list_channels ↓

AI agents call teams_list_channels to retrieve information from Sage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries and retrieves channel information from a Microsoft Teams team. It performs a read-only operation that returns existing data without creating, modifying, deleting, or executing any actions. The blast radius is minimal: an attacker could enumerate team channels but cannot modify team structure, delete channels, or affect team operations.

From the tool's definition Tool name is 'teams_list_channels' and description states 'List channels in a team' — a pure retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access teams_list_channels gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for teams_list_channels:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "teams_list_channels": {}
  }
}

teams_list_channels is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Sage MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the teams_list_channels tool do? +

List channels in a team. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on teams_list_channels? +

Register the Sage 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 Sage MCP. Nothing to install.

What risk level is teams_list_channels? +

teams_list_channels is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit teams_list_channels? +

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.

How do I block teams_list_channels completely? +

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.

What MCP server provides teams_list_channels? +

teams_list_channels is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sage MCP tool call.

Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.