teams_send_channel_message

SERVERLocal SOURCElocal-mcp

Medium RISK CLASS

Category Write

Parameters 43 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-local-mcp-local-mcp/teams-send-channel-message.md

WHAT IT DOES

What teams_send_channel_message does on Local

AI agents use teams_send_channel_message to create or update resources in Local, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local environment.

Parameter	Type	Required	Description
`text`	string	Yes	Plain-text message body
`confirm`	boolean	—	Set true to send; false returns preview
`team_id`	string	Yes	Team ID from teams_list_teams
`channel_id`	string	Yes	Channel ID from teams_list_channels

Parameters from the server's own tool schema.

RISK

Why teams_send_channel_message is rated Medium

This tool creates new messages in Teams channels, which is a reversible write operation. Severity is high because: (1) it can broadcast messages to multiple team members simultaneously; (2) an AI agent misuse could send unintended/sensitive messages to colleagues; (3) it has a preview-then-confirm pattern showing awareness of risk, but confirmation depends on agent logic.

From the tool's definition Sends a text message to a Microsoft Teams channel via Graph API; requires Chat.ReadWrite / ChannelMessage.Send permissions; first call returns preview, set confirm=true to send.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs teams_send_channel_message 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_send_channel_message, this is the rule to start with:

teams_send_channel_message Rate-limited

teams_send_channel_message stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "teams_send_channel_message": {
      "limits": [
        {
          "counter": "teams_send_channel_message_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every teams_send_channel_message call is checked against it from then on.

FAQ

Questions about teams_send_channel_message

What does the teams_send_channel_message tool do? +

Sends a text message to a Microsoft Teams channel via Graph API. Requires connect_m365_account with Chat.ReadWrite / ChannelMessage.Send permissions. team_id and channel_id must come from teams_list_teams / teams_list_channels. First call returns a preview; set confirm=true to send. It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does teams_send_channel_message accept? +

teams_send_channel_message accepts 4 parameters: text, confirm, team_id, channel_id. Required: text, team_id, channel_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on teams_send_channel_message? +

Register the Local MCP server in PolicyLayer and add a rule for teams_send_channel_message: 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.

What risk level is teams_send_channel_message? +

teams_send_channel_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit teams_send_channel_message? +

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

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

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

KEEP EXPLORING

More on Local, and thousands of servers like it.

This server

All 234 Local tools →

Across the catalogue

sms_send on Twilio SMS MCP Server →send-draft on Meme MCP Server →mail_send_draft on Apple Apps MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →