New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

teams_get_channel

Get details of a specific channel in a team

SERVERSage MCP SOURCEsagemcp/sagemcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/teams-get-channel.md

What teams_get_channel does on Sage MCP

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

Why teams_get_channel is rated Low

This tool retrieves channel information without creating, modifying, or deleting data. It has no side effects and presents minimal risk if misused by an agent—it can only expose existing channel metadata that an authenticated user would already have access to via normal OAuth authentication.

From the tool's definition Tool name and description indicate retrieval only: 'Get details of a specific channel in a team'. The verb 'get' and the absence of any modification language (create, update, delete, send) establish this as a read-only operation.

Questions about teams_get_channel

What does the teams_get_channel tool do? +

Get details of a specific channel 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_get_channel? +

Register the Sage MCP server in PolicyLayer and add a rule for teams_get_channel: 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_get_channel? +

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

Can I rate-limit teams_get_channel? +

Yes. Add a rate_limit block to the teams_get_channel 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_get_channel completely? +

Set action: deny in the PolicyLayer policy for teams_get_channel. 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_get_channel? +

teams_get_channel 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.

More on Sage, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sage's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.